Regardless of whether I set the sse use-flag to "sse" or "-sse", I see the following kind of lines: <cut> g++ -O3 -fomit-frame-pointer -ffast-math -fstrength-reduce -DARCH_X86 -mmmx -m3dnow -march=i686 -msse -mfpmath=sse -DBUILD_SSE_OPTIMIZATIONS -Wall -DENABLE_NLS -DHAVE_CONFIG_H -D_REENTRANT -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Ilibs/soundtouch -Ilibs -c -o libs/soundtouch/SoundTouch.o libs/soundtouch/SoundTouch.cpp </cut> Notice the -msse -mfpmath=sse -DBUILD_SSE_OPTIMIZATIONS flags. And the lines above are an excerpt from the output of a compile with USE="-sse". Sse is enabled in the make.conf, I'm doing this -sse/sse recompiling to figure out another ardour compiling error (bug #139784)
emerge info please
The -msse, -mfpmath=sse, -mmmx, -m3dnow (for x86) and other ppc related flags are set by detecting the cpu flags (as seen from /proc/cpuinfo), and are not controlled by a flag given to scons. I can see merit in this - and these are safe flags. (and it doesn't have anything to do with the problem reported in bug #139784) if you wish to change this I suggest you discuss it upstream, and the gentoo ebuilds will gladly follow. I'm reluctant to patch SConstruct since this will prove somewhat sisyphean to maintain. the scons option has changed to FPU_OPTIMIZATION (altivec on ppc, and sse for x86 and x86_64). I've updated the ebuild to set this if altivec or sse is set, and it is currently in CVS.
