On Wednesday 08 December 2010 12:19:10 Rosario Turco wrote: > I have done the compilation without error with > ../glibc-2.12.1/configure --prefix=/tools \ > --host = $ LFS_TGT --build =$(../ glibc-2.12.1/scripts/config.guess) \ > --disable-profile --enable-add-ons \ > --enable-kernel = 2.6.22.5 --with-headers=/tools /include \ > libc_cv_forced_unwind=yes libc_cv_c_cleanup= yes > libc_cv_visibility_attribute=yes libc_cv_broken_visibility_attribute=no > > but the make show the error linking > on the final > ../i686-lfs-linux-gnu/bin/ld: can not find lgcc > > What must i see?
Forgive me if I seem blunt; I must state this plainly and simply: you must see the incorrect syntax. Below, I show your incorrect syntax followed by the correct syntax, line by line. Three lines are correct; three are wrong. - Lines that start with BAD are your lines that contain invalid syntax. - Lines that start with FIX are lines I have corrected for you. - Lines that start with OK are your lines that are correct. Each line is presented on a single line. If needed, I'll repost the complete command with one command/option/item per line. ----------------------------- OK: ../glibc-2.12.1/configure --prefix=/tools \ BAD: --host = $ LFS_TGT --build =$(../ glibc-2.12.1/scripts/config.guess) \ FIX: --host=$LFS_TGT --build=$(../glibc-2.12.1/scripts/config.guess) \ OK: --disable-profile --enable-add-ons \ BAD: --enable-kernel = 2.6.22.5 --with-headers=/tools /include \ FIX: --enable-kernel=2.6.22.5 --with-headers=/tools/include \ BAD: libc_cv_forced_unwind=yes libc_cv_c_cleanup= yes FIX: libc_cv_forced_unwind=yes libc_cv_c_cleanup=yes \ OK: libc_cv_visibility_attribute=yes libc_cv_broken_visibility_attribute=no ----------------------------- The correct pieces of text are there. But something seems to have randomly added spaces here and there and dropped the last, but still important, backslash (\). If your text editor is messing up the syntax, you must use another text editor, one that uses a fixed-pitch (monospaced) font like Courier and doesn't reformat content. You will likely never see the errors if you are using a proportionally-spaced font like Arial, Helvetica, Times and the like. If your email program is screwing the syntax, use another program. I always use fixed-pitch even for email, except in very rare circumstances. A 50% hit ratio may be OK in baseball, but computer commands must be 100% correct for them to work properly. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
