On Sun, Dec 20, 2015 at 12:33:58PM -0800, Bryan Kadzban wrote: > Ken Moffat wrote: > > For the programs, on x86_64 pass 1 installs > > /tools/bin/x86_64-lfs-linux-gnu-gcc and pass 2 installs > > /tools/bin/x86_64-unknown-linux-gnu-gcc. > > Oh, right. > > That's the -pass2 gcc's config.guess printing x86_64-unknown-linux-gnu. So I > can see a couple ways to figure this out: either keep that script around and > rerun it whenever you need to figure out which gcc, or save the output > somewhere during the -pass2 build. > > > The library /tools/lib/libcc1.so is installed by both, so once gcc pass 2 > > has been installed it is ok to check that that lib does not link to the > > host. > > ...Oh, you need to run this before -pass2 as well, to see if it's there. > Right, OK. That makes it a lot harder than what I was thinking. Hmm... > > Ship the compiler's config.guess with the script maybe? Have to keep it up to > date though. > > (Plus what Bruce was just saying. If it's simple maybe it's OK, but this is > getting more complicated now...) >
Now that I have really managed to attach the scripts, I will just note that I've hardcoded the known names, the script is supposed to be self-contained so any extra vaiants could be added, but shipping config.guess is way OTT. But based on what Bruce said, I think he is going to NAK it. Not my problem, I now know how to build and debug LFS. I will also note that the script to check that nothing was missed is fairly useless if nobody has checked that nothing links to the host. ĸ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
