matthew gruda wrote: We prefer you not top post.
> $ cat `dirname $(gcc --print-libgcc-file-name)`/specs: That looks OK. > On Sun, Jan 6, 2013 at 12:57 PM, Bruce Dubbs <[email protected]> wrote: >> Lets break this down: >> >>> LIBRARY_PATH=/tools/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/: >>> /usr/lib/../lib64/: >>> /tools/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/ >>> ../../../../x86_64-unknown-linux-gnu/lib/: >>> /usr/lib/ >> >>> COLLECT_GCC_OPTIONS='-v' '-v' '-mtune=generic' '-march=x86-64' >>> /tools/libexec/gcc/x86_64-unknown-linux-gnu/4.7.1/collect2 >>> --eh-frame-hdr >>> -m elf_x86_64 >>> -dynamic-linker /lib64/ld-linux-x86-64.so.2 >>> /usr/lib/../lib64/crt1.o >>> /usr/lib/../lib64/crti.o >>> /tools/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/crtbegin.o >>> -L/tools/lib/gcc/x86_64-unknown-linux-gnu/4.7.1 >>> -L/usr/lib/../lib64 >>> -L/tools/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/ >>> ../../../../x86_64-unknown-linux-gnu/lib >>> /tmp/ccm2lzhu.o >>> "" I don't save this file in my logs, but the above "" looks suspicious. >>> -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc >>> --as-needed -lgcc_s --no-as-needed >>> /tools/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/crtend.o >>> /usr/lib/../lib64/crtn.o >>> /tools/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/ >>> ../../../../x86_64-unknown-linux-gnu/bin/ld: >>> cannot find : No such file or directory This is unusual. What can't it find? I think the empty string above. What is the result of: $ find /tools -name ld\* -type f -exec ls -l {} \; -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
