Ken Moffat wrote: > At last, my build of LFS-7.0 is underway. In chroot, gcc crapped > out because mpc had not installed a shared libmpc.so, and as is my > wont, I'd hidden the static libmpc.a. Turns out that mpc-0.9 > thought shared libs weren't supported: > > checking whether the gcc linker (/tools/x86_64-unknown-linux-gnu/bin/ld -m > elf_x86_64) supports shared libraries... ./configure: line 8413: : supported > targets:.* elf: command not found no > > Fortunately, google knows about this - thread starts at > http://lists.gforge.inria.fr/pipermail/mpc-discuss/2011-February/000809.html > and the workaround is to unset CFLAGS. > > So, I presume that nobody else uses CFLAGS when building LFS - who > would have thought that -O2 would have such detrimental effects ?
I never set any flags for my reference builds. I was just reviewing make tonight and re-learned that there is a difference between MYVAR=abc make and make MYVAR=abc of course it also depends on how the variable is used in the Makefile. However if you set CFLAGS="O3" to something and the Makefile uses CFLAGS="O2 -someotheroption", setting CFLAGS may just remove -someotheroption and break the build. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
