> Normally if you configure GCC and the binutils with the exact same > prefix, and install both, then GCC will use the ld built by the > binutils. This seems to be not the case for me. Any idea why? > > /home/afbacher/LFS71/lfs84/usr/bin/gcc dummy.c > > -B/home/afbacher/LFS71/lfs84/usr/ -v -Wl,--verbose >| dummy.log 2>&1 > > The -B option has to name the directory where ld is found. In this > case it seems that that should be /home/afbacher/LFS71/lfs84/usr/bin/ > , which is not what you show here. This worked for my simple test case (thanks!), but not for my main application. But now I'm really confused. The gcc manual says: ####### This option specifies where to find the executables, libraries, include files, and data files of the compiler itself. The compiler driver program runs one or more of the subprograms cpp, cc1, as and ld. It tries prefix as a prefix for each program it tries to run, both with and without `machine/version/' (see Target Options). ####### The executable, library, include and data files are in ..../bin, ..../lib, ..../include and so forth. How does specifying ..../usr/bin allow gcc to find the stuff in lib, include and so forth? Alan
