Ian Lance Taylor wrote: > >> ... If you run "gcc -print-search-dirs" it will print the > >> directories it searches for programs. One of those directories > ought > >> to contain a binary named "ld" installed by the GNU binutils. > > > > In the "programs:" list, the path to ld is not listed. It should be > something like: > > > > ..../usr/bin/ld > > > > All of the entries are something like this: > > > > ..../usr/lib/gcc/x86_64-unknown-linux-gnu/4.7.1 > > The GNU binutils should install a program named "ld" in a directory > that looks something like PREFIX/TARGET/bin, in addition to the one > installed in PREFIX/bin. GCC should look in PREFIX/TARGET/bin. There is no ld in PREFIX/TARGET/bin. In fact, there is no PREFIX/TARGET/bin -- only PREFIX/bin. There is PREFIX/lib/gcc/TARGET/4.7.1 which contains cc1, crtbegin.o, libgcc.a and a bunch of other necessary files. I'm now wondering if I missed something during the compilation of all the programs necessary for gcc, including binutils and glibc. Any suggestions? > > Am I missing something obvious, or is this such common knowledge in > the user community that it doesn't seem necessary to state? Or should > the manual be revised to include what you've told me? If so, how might > that be done? > > When I look at the docs for -B it appears accurate to me. I think you > are saying that you found it confusing because you didn't understand > how it worked. Probably so. > But the fact remains that, as far as I can see, it does > work as the manual describes. We could extend the manual to explain > how it works, but I suspect that for most users that would be more > confusing than helpful. Still, better documentation is always good, so > if you have a concrete suggestion that would be great. I will think about doing that and, when I get a chance, offer a concrete suggestion. Again thanks! Alan
