Created attachment 401516 [details] emerge info x86 no_forced-sse2 patch fails to activate & consequently the configuration fails
Created attachment 401518 [details] results of attempted patch
Created attachment 401520 [details] build log x86
Created attachment 401522 [details] environment file
It seems that this patch is no longer needed since the related and broken sse2 code in configure.in is gone. This also happened in ruby 2.2 so I guess this got backported. Could you confirm if ruby-2.1.6 builds correctly with "CPU_FLAGS_X86=sse2"? I would assume that it does, and in that case we can drop both the patch and the flag altogether for this version.
(In reply to Hans de Graaff from comment #4) > It seems that this patch is no longer needed since the related and broken > sse2 code in configure.in is gone. This also happened in ruby 2.2 so I guess > this got backported. > > Could you confirm if ruby-2.1.6 builds correctly with "CPU_FLAGS_X86=sse2"? > I would assume that it does, and in that case we can drop both the patch and > the flag altogether for this version. I'll give that a go,but that particular machine doesn't have the sse2 flag for the cpu,it's an amd athlon-xp
That didn't work so well.I echoed CPU_FLAGS_X86=sse2 to package use but portage in it's wisdom changed it to -sse2 in the configure.
(In reply to Geoff Madden from comment #5) > I'll give that a go,but that particular machine doesn't have the sse2 flag > for the cpu,it's an amd athlon-xp I understand, but in this specific case the sse2 flag is just there to avoid the broken patch. What I want to know is whether ruby successfully compiles in this case.
(In reply to Hans de Graaff from comment #7) > (In reply to Geoff Madden from comment #5) > > > I'll give that a go,but that particular machine doesn't have the sse2 flag > > for the cpu,it's an amd athlon-xp > > I understand, but in this specific case the sse2 flag is just there to avoid > the broken patch. What I want to know is whether ruby successfully compiles > in this case. in a word no. on my 64 bit machines which are using ruby22 there is not a hassle,only on the x86
The broken sse2 patch has been removed in ruby 2.1.6-r1. I believe this should fix the issue. Please reopen the bug if there are still issues with this version.
