Created attachment 316635 [details] emerge info On old CPU, which do not support SSE2 instructions, google-chrome don't start properly, because embedded PepperFlash player compile with this instruction. If Flash not needed problem solved by deleting the folder '/opt/google/chrome/PepperFlash'.
Um, portage highly discourages running w/o mounted proc (i.e. chroot/install situations). So we might consider an pkg_setup (or pkg_preinstall) check for [ grep ^flags /proc/cpuinfo | grep " sse " ] In general I'm quite sure that this should work on amd64/x86 kernels, but for example arm has another format (no sse), and I have no idea of non-linux (i.e. bsd). Maybe we should dig gentoo-dev-ml or ask any wise guy, whether or not such an test is an bad thing. google-chrome is - besides all - binary amd64/x86 only. But I can recall an discussion about pulseaudio on arm regarding conditional patching for missing features of armv5 compared to armv6, with an NACK on such tests by maintainer. ... Processor : ARMv6-compatible processor rev 7 (v6l) BogoMIPS : 697.95 Features : swp half thumb fastmult vfp edsp java tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xb76 CPU revision : 7 Hardware : BCM2708 Revision : 0002 Serial : 000000001304e7e7
I think removing the file in pkg_preinst would be fine.
+ 02 Jul 2012; Mike Gilbert <floppym@gentoo.org> + google-chrome-20.0.1132.47_beta144678.ebuild, + google-chrome-20.0.1132.47_p144678.ebuild, + google-chrome-21.0.1180.15_alpha144745.ebuild: + Rename PepperFlash plugin if CPU does not support SSE2. Bug 424147. +
