It seems that Ruby is fairly tolerant of compiler optimizations at build-time (I was able to build with CFLAGS="-march=pentium2 -O3 -pipe -fforce-addr -falign-functions=4 -ffast-math" which is clearly pushing the envelope a bit for a default CFLAGS setting (I'll actually test ruby later when I have some clue as to how that can be properly done.) However, one very common optimization recommended as both beneficial and very safe in the community is -fomit-frame-pointer, which in this causes the build to fail and does so consistently. I've been able to build most everything else with this optimization enabled along with the others listed above, but Ruby would have none of it. The error given seemed to change depending upon which other optimizations were enabled, but invariably the build would fail.
Don't we have a ruby team?
*** This bug has been marked as a duplicate of 8290 ***
