From: Sasha Levin <levinsasha928@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: mingo@elte.hu, gorcunov@gmail.com, asias.hejun@gmail.com,
kvm@vger.kernel.org
Subject: Re: [PATCH] kvm tools: Link ld.so.conf to the file on the host
Date: Tue, 06 Dec 2011 15:37:05 +0200 [thread overview]
Message-ID: <1323178625.8489.2.camel@lappy> (raw)
In-Reply-To: <alpine.LFD.2.02.1112061523180.1646@tux.localdomain>
On Tue, 2011-12-06 at 15:24 +0200, Pekka Enberg wrote:
> On Tue, 6 Dec 2011, Sasha Levin wrote:
> > This enables the custom rootfs to run executables which have dylibs located
> > in non standard paths by taking these settings from the host.
> >
> > Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
> > ---
> > tools/kvm/builtin-setup.c | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/tools/kvm/builtin-setup.c b/tools/kvm/builtin-setup.c
> > index fb8a1b3..ecdf76b 100644
> > --- a/tools/kvm/builtin-setup.c
> > +++ b/tools/kvm/builtin-setup.c
> > @@ -120,6 +120,7 @@ static const char *guestfs_symlinks[] = {
> > "/lib64",
> > "/sbin",
> > "/usr",
> > + "/etc/ld.so.conf",
> > };
> >
> > static int copy_init(const char *guestfs_name)
>
> This doesn't fix the issue I have with
>
> kvm tools: Split custom rootfs init into two stages
>
> i.e. I still see:
>
> ./kvm run tests/pit/tick.bin
> Fatal: Failed linking stage 2 of init.
> make: *** [check] Error 128
Thats unrelated, this patch is supposed to get gnome apps to work in the
custom rootfs :)
--
Sasha.
prev parent reply other threads:[~2011-12-06 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 13:01 [PATCH] kvm tools: Link ld.so.conf to the file on the host Sasha Levin
2011-12-06 13:24 ` Pekka Enberg
2011-12-06 13:37 ` Sasha Levin [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=1323178625.8489.2.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).