Summary: | sys-devel/gcc-5.3.0[jit]: stage2/stage3 comparison fails when using <=gcc-4.9 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | bertrand, de.techno, mark+gentoobugs, skobkin-ru, vsuharnikov |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log.bz2 |
Description
Juergen Rose
2015-12-21 19:56:22 UTC
'USE=-jit emerge -v1 sys-devel/gcc' works like a charm. It seems, that the issue disappeared after switching to gcc-5.3.0. (In reply to Juergen Rose from comment #2) > It seems, that the issue disappeared after switching to gcc-5.3.0. Confirmed. gcc-5.3.0 (+jit) fails to build with gcc-4.9.3 but succeeds when building with gcc-5.3.0 Seconded. Building with gcc-4.9.3 causes gcc-5.3.0 to fail the stage 2-3 comparison with the +jit use flag. Built just fine with -jit. Before I saw this bug I was worried that my system had bad RAM again... *** Bug 570558 has been marked as a duplicate of this bug. *** I have the same problem. Does this still affect gcc 5.4 ? *** Bug 574022 has been marked as a duplicate of this bug. *** I suggest closing it as obsolete. The USE=jit is masked for quite a while as: # Michał Górny <mgorny@gentoo.org> (14 May 2016) # (on behalf of QA team) # sys-devel/gcc[jit]: # - violates strict multilib rules, #569608 # - causes collisions between multiple gcc versions, #583010 # Masking the flag until it is fixed. sys-devel/gcc jit We can revise it once/if other jit-related problems are fixed. |