A quick look in autoconf-lib-link/ suggests that @CFLAGS@ are picked
up during configure, so if we are going to do it more cleanly we
will either pass CC="gcc ${BUILD64} -fPIC" or CFLAGS="-fPIC" to
configure. Either of these will probably cause the whole compile to
use -fPIC, I hope that is not a problem, but it needs to be tested.
I guess CFLAGS is a safer idea, if it works.
Anybody able to test any of this ?
I tried go moko's solution and both of yours. In all three cases, it
passed all of the tests, and in all three cases there were 224 tests
instead of the 40 that get done when following CLFS Version
1.0.0rc3-x86_64-Multilib. Also, whether or not I use the sed command
at the beginning of the section (10.42. Gettext-0.14.5 64 Bit) in CLFS
doesn't seem to matter.
Personally, assuming that all three ways are equal, I'd prefer
CC="gcc ${BUILD64} -fPIC" CXX="g++ ${BUILD64} -fPIC" \
./configure --prefix=/usr --libdir=/usr/lib64
over having to set CFLAGS and/or CXXFLAGS since by default I have them
set for optimizations for my computer. Also, if the sed command
doesn't matter, then it should probably be removed.
- Jonathan Davis
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
