On Sat, Dec 19, 2015 at 12:45:38PM +0100, Pierre Labastie wrote: > On 19/12/2015 03:29, Ken Moffat wrote: > > > > But for the libraries, I just got pain. As well as the tcl libs > > linked to /lib, I discovered that *many* libraries from glibc, and > > also libstdc++, are linked to /lib, and a couple are also linked to > > /usr (libgcc_s : we handle that one when we enter chroot. > > > > That's amazing: running your script after stopping a build at gcc-pass2 (I > have not tried to build a bogus package), I get no output. Of course, PATH has > to be set to /tools/bin:$PATH, otherwise, it is host's ldd which is run, and > everything is found in /lib. But I guess you did set your PATH, otherwise, you > would have gotten output for programs as well. > > Pierre Pierre, thanks for that - I suspect /tools/bin was _not_ on my PATH. I didn't try that latest version of the script until I'd mis-built tcl.
Maybe I'll give it another try from the beginning, or just force the PATH in that script and retry it for where it currently is. Too many non-computer problems at the moment, might not happen. ĸen -- This email was written using 100% recycled letters. -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
