On February 19, 2005 06:41 pm, Garrett Schure wrote: > 5.7.1 Glibc: > --without-selinux for --disable-selinux
That one was fixed earlier today. > 5.13.1 Binutils pass 2 > --libdir=/tools/lib for --with-lib-path=/tools/lib > > Fixed: gcc wouldn't work from within the chroot environment, > even though the "sanity check" swore up and down that I > had /tools/lib compiled in O.K. Do you have more info why GCC wouldn't work? --libdir and --with-lib-path are two entirely different settings. --libdir would specify a directory where libraries get installed, whereas --with-lib-path sets the default LIB_PATH: where the system will look for libraries to link with. libdir is just an installation directory where lib-path changes how the linkder (ld) actually does its work. Changing this may not have the desired effects. The reason you had to change this indicates that you may not have installed the toolchain properly (gcc and glibc are the other two packages to look at). If you can provide more information why GCC doesn't work from within chroot we can help you with it. Please send follow-ups to the lfs-support mailinglist. > 5.21 Grep > Perhaps add configure option --libdir=/tools/lib. > > Fixed: glibc compilation from chroot said "working compiler May or may not be tied in with your other problem. -- Gerard Beekmans /* If Linux doesn't have the solution, you have the wrong problem */ -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
