On Tue, Apr 16, 2002 at 10:32:15AM +0100, [EMAIL PROTECTED] wrote: > On Tue, Apr 16, 2002 at 10:36:54AM +0200, Michael Palme wrote: > > [...] also replaced the old libs (libc, libm, > > libcrypt...) in /lib with the libs from my toolchain > > In your ramdisk, try to create a link so that your build > system's library points to the actual library, i.e.: > > On your build system, if your toolchain is in > /opt/gcc/arm-linux, and you put your libs in /lib, then > mkdir -p /opt/gcc > ln -s / /opt/gcc/arm-linux > > That way /opt/gcc/arm-linux/lib points to the proper libc. > > That has something to do with the dynamic linker (ld-linux) > looking for libs where it was built rather than in the > expected place, which I can't remember if it's a bug in libc > or expected. Anyway, that worked for me.
You can also edit the ld.so binary. That's what I did with the LART ramdisk. (hmm, need to document that somewhere). Erik -- J.A.K. (Erik) Mouw, Information and Communication Theory Group, Faculty of Information Technology and Systems, Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands Phone: +31-15-2783635 Fax: +31-15-2781843 Email: [EMAIL PROTECTED] WWW: http://www-ict.its.tudelft.nl/~erik/ _______________________________________________ http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm http://www.arm.linux.org.uk/armlinux/mailinglists.php Please visit the above addresses for information on this list.
