From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] fix for qemu-* looping forever on symlinks (patch attached)
Date: Sat, 15 Jul 2006 23:39:16 +0100 [thread overview]
Message-ID: <200607152339.16734.paul@codesourcery.com> (raw)
In-Reply-To: <5b5833aa0607151534w266d1164if03f75ff1de3978b@mail.gmail.com>
On Saturday 15 July 2006 23:34, Anderson Lizardo wrote:
> On 7/13/06, Paul Brook <paul@codesourcery.com> wrote:
> > The whole point of the -L option is so that it picks up target shared
> > libraries, eg. in lib and usr/lib. By my reading your patch makes the -L
> > option do absolutely nothing, which can't be right.
> >
> > The proper fix is to do the lookups when a file is accesses (possibly
> > with caching) not pre-scan the whole tree.
>
> Is it possible to use the same cache format as ld.so
I don't think there's any point having a persistent cache, and I don't thin
the ld.so format would be particularly appropriate either. Qemu just does
straight filename translation.
Paul
prev parent reply other threads:[~2006-07-15 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 2:31 [Qemu-devel] fix for qemu-* looping forever on symlinks (patch attached) Michael Gilbert
2006-07-14 3:30 ` Paul Brook
2006-07-15 22:34 ` Anderson Lizardo
2006-07-15 22:39 ` Paul Brook [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200607152339.16734.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.