chromium-drop_sse2.patch failed on www-client/chromium-9999. i'll attach chromium-drop_sse2.patch.out in a sec. Reproducible: Always Steps to Reproduce:
Created attachment 227767 [details] chromium-drop_sse2.patch.out chromium-drop_sse2.patch.out
I had some conversation with the chromium-guys: <rubenbb> hmm, reading the relevant chromium ticket, it looks like that patch is completely unnecessary - code.google.com/p/chromium/issues/detail?id=9007 <rubenbb> or even http://code.google.com/p/chromium/issues/detail?id=9007 <rubenbb> if I were you, I'd just remove that patch and build and complain to whoever left that in
Any status on the removal of the patch?
Here are some flags that get appended to CFLAGS without this patch (on i386): -m32 -mmmx -march=pentium4 -msse2 -mfpmath=sse So it is definitly still needed, working on a new version. In Gentoo we do mind about build systems forcibly setting CFLAGS like that ;)
Patch updated (+files/chromium-drop_sse2-r1.patch), thanks for the report!
Created attachment 229897 [details] new patch.out
Similar problem with the new patch (attached). Reopen if anyone else can duplicate this (or tell me to create a new bug)
(In reply to comment #7) > Similar problem with the new patch (attached). Reopen if anyone else can > duplicate this (or tell me to create a new bug) > I am able to duplicate this bug with the new patch, unfortunately.
I guess it's already time for -r2 version of the patch, thanks for the notification
Created attachment 230273 [details, diff] chromium-drop_sse2-r2.patch Here is a new patch that applies better than the -r1 patch.
Even better: "Add a gyp flag for disabling sse2. This makes it easier for distros to disable sse2." I've updated -9999 ebuild, thanks for the notification. And this time I think this will stay fixed as we do not need to patch anymore :)
Great, this now works for me. Thanks a lot!
