| Summary: | sys-devel/gcc-5.1: new default ABI: cxx11 incompatible with GCC-4.9 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | LE GARREC Vincent <gentoo.bugzilla> |
| Component: | [OLD] GCC Porting | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | Christopher.Lundgren, jospezial, mgorny, mrloquax, O01eg, patrick, tdalman, zx2c4 |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=550432 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 550432 | ||
| Bug Blocks: | |||
|
Description
LE GARREC Vincent
2015-04-26 10:31:06 UTC
Hi Vincent, (In reply to LE GARREC Vincent from comment #0) > According to https://wiki.gentoo.org/wiki/Upgrading_GCC, running "emerge > -eav system" and "emerge -eav world" is old school. But do you think that > with this new change of the default ABI, I should emerge the whole world ? There are some critical bugs that will most likely prevent you from doing that. For instance, neither Xorg, nor Python 3 are properly working at the moment. > Actually, I didn't do it but I can easily. But my main problem is that GCC > 5.1 is not compatible with GCC 4.9. Have you tried to use -std=gnu++98 ? You can either selectively upgrade your packages, or wait until everything has stabilized with GCC 5.1. Yes you need to rebuild world, this is a major version bump. No you should not be using gcc-5.1 at this point unless you know what you're doing. revdep-rebuild support to try and automate is tracked by bug 550432 *** Bug 547954 has been marked as a duplicate of this bug. *** *** Bug 556100 has been marked as a duplicate of this bug. *** *** Bug 553702 has been marked as a duplicate of this bug. *** *** Bug 553700 has been marked as a duplicate of this bug. *** *** Bug 551392 has been marked as a duplicate of this bug. *** *** Bug 548730 has been marked as a duplicate of this bug. *** *** Bug 548728 has been marked as a duplicate of this bug. *** *** Bug 541470 has been marked as a duplicate of this bug. *** *** Bug 560846 has been marked as a duplicate of this bug. *** |