|
Bugzilla – Full Text Bug Listing |
| Summary: | mozjs17 fails to build with GCC7 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Martin Liška <martin.liska> |
| Component: | Firefox | Assignee: | E-mail List <bnc-team-mozilla> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | wolfgang |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 1030236 | ||
|
Description
Martin Liška
2017-04-05 09:20:28 UTC
We should get rid of unmaintained mozjs17 in TW. Need to find out which component still uses it and try to move them to a more recent version. (In reply to Wolfgang Rosenauer from comment #1) > We should get rid of unmaintained mozjs17 in TW. > Need to find out which component still uses it and try to move them to a > more recent version. Hello. Any update on that? Looks there's just few last packages blocking the Staging:C project which changes default compiler to GCC7. Ok, fixing the issue is actually very simple. A simple patch from trunk is needed. I'll create SR soon. Actually I was hoping to create some pressure onto consumers to migrate away from mozjs17 which is horribly outdated and we want to get rid of asap. Fixing it does not help with that :-( (In reply to Wolfgang Rosenauer from comment #4) > Actually I was hoping to create some pressure onto consumers to migrate away > from mozjs17 which is horribly outdated and we want to get rid of asap. > Fixing it does not help with that :-( I see, well I'm motivated to have staging C with new GCC ready as soon as possible. That said: osc whatdependson openSUSE:Factory:Staging:C mozjs17 standard x86_64 mozjs17 : colord gconf2 installation-images pcsc-lite polkit polkit-default-privs rpmlint-mini yast2-country If at least these packages will be migrated, then it can go in Factory and other people will be forced to fix their packages. > polkit
I took a look at polkit package. Problem is that last release was done in Jun 2015 and currently there're various patches that port that to mozjs24, but it's no a trivial set of patches we can backport :/
Fix has landed in Factory, thus closing as fixed. |