FFe: upload gcc-4.8 to raring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc-4.7 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Raring |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[filed for gcc-4.7, because gcc-4.8 isn't yet available in LP]
Proposing to upload gcc-4.8 to raring (as packaged in the ubuntu-
Rationale: Make gcc-4.8 available to developers in the latest Ubuntu release for development purposes. GCC-4.8 will become the default GCC in the s-series, and the next LTS release, so exposing this earlier to (not only Ubuntu) developers might be good idea. This is not a proposal to make gcc-4.8 the default at this point (well, maybe except for gccgo, which doesn't have any reverse build dependencies). http://
The runtime libraries in GCC didn't bump soversions in 4.8 (except for libgo and libgcj). These are the packages then built from the gcc-4.8 sources instead of the gcc-4.7 sources. The compilers stay the same.
The proposal includes updating the gcc-4.8 package to a 4.8.1 release as a stable release update for raring.
I'm running a raring desktop with the binaries installed from the gcc-4.8 source package since January without problems. Same for armhf build environments.
Changed in gcc-4.7 (Ubuntu Raring): | |
milestone: | none → ubuntu-13.04-beta-1 |
description: | updated |
Changed in gcc-4.7 (Ubuntu): | |
status: | Confirmed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.