Neal Murphy wrote: > On Sunday 05 December 2010 10:55:13 Rosario Turco wrote: >> ../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 libc_cv_c_cleanup = yes = yes >> libc_cv_visibility_attribute=yes libc_cv_broken_visibility_attribute = no > > I surely hope the embedded spaces and lost hyphens are a result of language > translation. Otherwise, I'm not sure that command has any chance of working. > Options are introduced with "--", not "-". The option names are lower case > (though this *might* not matter). The configure command's fifth line is > missing a "\" continuation character, and it has an extra yes. Correcting all > that results in: > > ../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 libc_cv_c_cleanup=yes \ > libc_cv_visibility_attribute=yes libc_cv_broken_visibility_attribute=no > > Syntax is extremely important. As with humans, if you don't 'speak' the > language correctly, the computer will not do what you expect.
I agree. Computers do exactly what you tell them to do, not what you think you told them to do. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
