Summary: | www-client/chromium install fails on x86 to erroneous handling of sse/mmx compile flags in ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tor Rune Skoglund <trs> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | trs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tor Rune Skoglund
2019-01-04 12:47:09 UTC
Who is "we"? Is this bug report from the Borg collective? ;-) > Then, later in the same ebuild, at line 541, these added flags and also the original CFLAGS are removed by the strip-flags call. Sounds like I need to move the x86 CFLAGS logic after the strip-flags call. > In our opinion, the ebuild should not try to be to "smart" in handling compile flags, but leave that up to the user to set those that should be necessary to make it work. I suspect you have little experience in dealing with Gentoo bug reports. Gentoo users do all sorts of crazy things, and that makes my job more difficult. Calling strip-flags makes that a bit less difficult. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=91f2491c60e83b240a777abb7630fa81a65ecc2a commit 91f2491c60e83b240a777abb7630fa81a65ecc2a Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2019-01-05 05:07:02 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2019-01-05 05:07:02 +0000 www-client/chromium: call strip-flags before appending flags Closes: https://bugs.gentoo.org/674500 Package-Manager: Portage-2.3.53_p6, Repoman-2.3.12_p37 Signed-off-by: Mike Gilbert <floppym@gentoo.org> www-client/chromium/chromium-71.0.3578.98.ebuild | 35 +++++++++++----------- .../chromium/chromium-72.0.3626.28-r1.ebuild | 35 +++++++++++----------- 2 files changed, 36 insertions(+), 34 deletions(-) |