On Sat, 2006-01-28 at 08:32 -0800, Dan Nicholson wrote:
> On 1/27/06, Greg Schafer <[EMAIL PROTECTED]> wrote:
> > Ever looked at a build log of GCC itself? Guess what? -B.
>
> /tools/src/build/gcc-build/gcc/xgcc -B/tools/src/build/gcc-build/gcc/
> -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ ...
>
> Seems gcc thinks it's OK to search for libraries with -B. This came
> from the line to compile libgcc_s.so in chroot.
>
> Not meaning to fan flames, but -B doesn't look so evil.
You've picked a good example here.
When you are doing an old style cross-toolchain build
(ie: not using a sysroot, all target libraries and includes installed
under /prefix/target/lib /prefix/target/lib64
/prefix/target/{include,sys-include} )
the above "-B/prefix/target/lib" generates an interesting error when
multilib, the 32bit startfiles get linked into the 64bit libgcc.
You could possibly label its use a bug, especially as it does not
need to be specified ( standard lib search path )
We actually patch that out in cross-lfs.
Best regards
Ryan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
