I don't know if this counts as bug, but as everything else compiled without problems (and I read about removing too agressif flags) here it is: when using the following C(XX)FLAGS ruby won't compile: CFLAGS="-march=pentium-mmx -mcpu=pentium-mmx -O3 -pipe -fforce-addr -fomit-frame-pointer -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4" I had problems installing ruby afterwords, but I think that the problem was the existing /var/tmp/portage/ruby* tree. Can't really remember everything I tried, but I finally was able to compile it, after deleting /var/tmp/portage/ruby* and setting C(XX)FLAGS to: "-march=pentium-mmx -mcpu=pentium-mmx -O3 -pipe" system ist 1.3 (1.4?) sys-devel/gcc Latest version available: 3.2-r1 Latest version installed: 3.2-r1
You will probably run into problems with other packages later in your gentoo experience with such aggressive flags :)
Your flags are too aggressive. We cannot start filtering out all flags that may cause the ruby ebuild to fail at this stage. We may end up later doing a more formal, structured optimisation flag testing of all packages, but that's still a long way off. In the interim, be advised that aggressive optimisation flags may be hazardous to your health and no warranty is implied, etc, etc ;P
