Hello

After adjusting the specs file GCC cant find correct path to the dynamic linker,
correct headers and Glibc start files. All previous steps were OK. "Sed" command
executed by copy-paste method.

Compiles the dummy.c produces an error instead of the output file. That's the
last line of the file dummy.log:

GNU assembler version 2.24 (i686-pc-linux-gnu) using BFD version (GNU Binutils)
2.24
COMPILER_PATH=/tools/libexec/gcc/i686-pc-linux-gnu/4.8.2/:/tools/libexec/gcc/i686-pc-linux-gnu/4.8.2/:/tools/libexec/gcc/i686-pc-linux-gnu/:/tools/lib/gcc/i686-pc-linux-gnu/4.8.2/:/tools/lib/gcc/i686-pc-linux-gnu/:/tools/lib/gcc/i686-pc-linux-gnu/4.8.2/../../../../i686-pc-linux-gnu/bin/
LIBRARY_PATH=/tools/lib/gcc/i686-pc-linux-gnu/4.8.2/:/tools/lib/gcc/i686-pc-linux-gnu/4.8.2/../../../../i686-pc-linux-gnu/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-v' '-mtune=generic' '-march=pentiumpro'
/tools/libexec/gcc/i686-pc-linux-gnu/4.8.2/collect2 --eh-frame-hdr -m elf_i386
-dynamic-linker /lib/ld-linux.so.2 /usr/lib/crt1.o /usr/lib/crti.o
/tools/lib/gcc/i686-pc-linux-gnu/4.8.2/crtbegin.o
-L/tools/lib/gcc/i686-pc-linux-gnu/4.8.2
-L/tools/lib/gcc/i686-pc-linux-gnu/4.8.2/../../../../i686-pc-linux-gnu/lib
/tmp/ccWnFMqi.o "" -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc 
--as-needed
-lgcc_s --no-as-needed /tools/lib/gcc/i686-pc-linux-gnu/4.8.2/crtend.o
/usr/lib/crtn.o
/tools/lib/gcc/i686-pc-linux-gnu/4.8.2/../../../../i686-pc-linux-gnu/bin/ld:
cannot find : No such file or directory
/tools/lib/gcc/i686-pc-linux-gnu/4.8.2/../../../../i686-pc-linux-gnu/bin/ld:
cannot find -lgcc_s
/tools/lib/gcc/i686-pc-linux-gnu/4.8.2/../../../../i686-pc-linux-gnu/bin/ld:
cannot find -lc
/tools/lib/gcc/i686-pc-linux-gnu/4.8.2/../../../../i686-pc-linux-gnu/bin/ld:
cannot find -lgcc_s
collect2: error: ld returned 1 exit status

What shall I do to continue building?

Sorry my bad Endlish. Regards.
Mark Kavalenkov.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to