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@xxxxxxxxx>
> > ---
> > 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.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
