| Summary: | www-client/chromium-bin failed to start | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | liu wenmao <marvelliu> |
| Component: | Current packages | Assignee: | Bernard Cafarelli <voyageur> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
liu wenmao
2009-09-09 04:12:48 UTC
I have a very similar problem that happened when portage only supplied chromium 4.0 binaries (working great with the 3.0 binaries). i used chrome using the method mentioned in http://blog.andreaolivato.net/open-source/google-chrome-natively-running-on-gentoo-linux.html. I found the first error remains, but illegal instrument error disappear, and chrome starts successfully. [14008:14008:5125017921:ERROR:/b/slave/chromium-rel-linux/build/src/chrome/browser/google_update_settings_posix.cc(73)]Not implemented reached in static bool GoogleUpdateSettings::GetLanguage(std::wstring*) Reverting back to 3.0 branch via ebuild provided in #278975 and building from source fixed my problem. Chrome works once again. Thanks for reporting your experiences with trying to run chromium-bin, assigning to maintainer. For the "Illegal instruction" problem, these binary snapshosts are optimized for Pentium-4 or higher, or more accurately SSE2. I was almost sure I had added a test/warning on this (almost), but now I'll really add it! Building from source does not show this problem, as the ebuild correctly sets CFLAGS for your arch (the 4.x version in bug #278975 will work too, when source tarballs are available) www-client/chromium-bin now checks SSE2 support (and dies if missing), and I've just added www-client/chromium-4.0.210.0_p26329 to the tree (with a tarball hosted on gentoo mirrors for now), so this should fix everything reported here? Thanks for the report! |