From: Luca Barbato <lu_zero@gentoo.org>
To: Jing Huang <jing.huang.pku@gmail.com>
Cc: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] Re: cross_container_support - progress report #9
Date: Thu, 02 Aug 2012 18:14:35 +0200 [thread overview]
Message-ID: <501AA76B.6050608@gentoo.org> (raw)
In-Reply-To: <CAK8mDgqSnJ5ZbB4odYEzY3oYQXBBRYhH7_EtDxVAcTTCRw6GXw@mail.gmail.com>
On 08/02/2012 05:23 PM, Jing Huang wrote:
> Hmm.. The root cause of this fault is:
>
> ./x86-program(built with dynamic libraries)
> -->load_elf_binary()
> -->open_exec("/lib/ld-linux.so.2");
>
> lxc chroot lacks of /lib/ld-linux.so.2. This problem is a difficult
> one. In my opinion, the following two steps are essential to solve it.
>
> 1. alter linker script to build x86-program using custom ld-linux.so.2
> path ( /target/lib/ld-linux.so.2 ).
>
Overriding it is an interesting task, for the time being try mixing
amd64 and arm binaries, they use /lib and /lib64 so it is fine.
> 2. switch dynamic libraries to custom paths.
> This point is relatively easy. I could use either LD_LIBRARY_PATH or
> ld.so.conf.
>
> "ldconfig /etc/ld.so.conf" is odd. I had altered ld.so.conf and
> env.d/00basic to exclude original library path(/lib, /usr/lib,
> /usr/local/lib), but the new generated cache file still include these
> paths.
> Unfortunately, linker will link libraries accroding to the ld cache
> file unless declare the DT_RPATH and LD_LIBRARY_PATH.
Yes, it is one of the issue to investigate.
lu
prev parent reply other threads:[~2012-08-02 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 15:45 [gentoo-soc] cross_container_support - progress report #9 Jing Huang
2012-07-31 19:30 ` [gentoo-soc] " Luca Barbato
2012-08-01 17:01 ` Jing Huang
2012-08-02 15:23 ` Jing Huang
2012-08-02 16:14 ` Luca Barbato [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=501AA76B.6050608@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=gentoo-soc@lists.gentoo.org \
--cc=jing.huang.pku@gmail.com \
/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