On Sun, Dec 20, 2015 at 11:26:53AM -0800, Bryan Kadzban wrote: > Ken Moffat wrote: > > On x86_64, gcc pass 2 installs x86_64-unknown-linux-gnu-gcc. On my > > previous 32-bit builds, it installed i686-pc-linux-gnu-gcc but I am not > > certain if that was because of some minor way in which I might have > > deviated (in the same way that I used to build glibc for i686), or whether > > the 32-bit compiler will always be i686 ? > > I am pretty sure it will be what we use for the magic cross-compiler --build / > --host / --target flags, or whatever config.guess prints if we don't use them. > > However, it looks like the -pass2 build is using the $LFS_TGT-gcc binary (that > -pass1 installed) already. I assume you've double checked that -pass2 > overwrites that binary? >
By binary, do you mean pogram or library ? 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. 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. ĸ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
