On 6/14/05, Raphael Melo de Oliveira Bastos Sales <[EMAIL PROTECTED]> wrote: > I think it is better to set sse on a USE flag so if a program is made > to use them (i.e. X.org), it can, but it doesn't affect the other > packages that weren't made with them in mind.
And, directly from the X.org ebuild, we can find this: # Recently there has been a lot of stability problem in Gentoo-land. Many # things can be the cause to this, but I believe that it is due to gcc3 # still having issues with optimizations, or with it not filtering bad # combinations (protecting the user maybe from themselves) yet. # # This can clearly be seen in large builds like glibc, where too aggressive # CFLAGS cause the tests to fail miserbly. # # Quote from Nick Jones <[EMAIL PROTECTED]>, who in my opinion # knows what he is talking about: # # People really shouldn't force code-specific options on... It's a # bad idea. The -march options aren't just to look pretty. They enable # options that are sensible (and include sse,mmx,3dnow when appropriate). # # The next command strips CFLAGS and CXXFLAGS from nearly all flags. If # you do not like it, comment it, but do not bugreport if you run into # problems. # # <[EMAIL PROTECTED]> (13 Oct 2002) strip-flags I think the quote from Nick Jones just reinforces my argument. Every gentoo user who likes to mess with every flag in gcc should at least read gcc's online documentation. Of course I have commented that out and compiled X.org with my normal cflags. I haven't found where strip-flags is defined to see what it really strips, but I have confidence in my cflags (-O2 -pipe -march=athlon64 -fomit-frame-pointer). -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ: 1406477 Rio de Janeiro - Brazil | -- gentoo-user@gentoo.org mailing list
