>On Thu, 4 Jul 2013 20:34:54 -0500 >Tyrin Price <[email protected]> wrote: > > > You can use CLFS instructions to build the 32-bit /tools directory > > and then put a link to /tools/lib/ld-linux.so.2 into /lib. > > > > This way, when the application requests the /lib/ld-linux.so.2 > > dynamic linker, it will get one and the linker will then use > > libraries in /tools for linking. > > The linker will automatically use libraries in /tools just by putting > a symlink to /tools/lib/ld-linux.so.2 into /lib? >
Yes. You will have two linkers. /lib/ld-linux-x86-64.so.2 will be part of the Glibc that lives in /lib. It will link against /lib/libc.so.6 and friends. /lib/ld-linux.so.2 will be part of the Glibc that lives in /tools/lib (or in my case /opt/linux32/lib) and will link against that library. One thing: make sure you don't mixup /lib/libc.so.6 and /tools/lib/libc.so.6 when building. This can happen if you set /tools/bin/gcc to try using /lib/libc.so. The symlink hack I suggested is only really usefull for running applications. It should never be used for building otherwise you run the risk of opening the gates of hell. -- You don't need an AI for a robot uprising. Humans will do just fine.
signature.asc
Description: PGP signature
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
