| 1 |
On Tue, Sep 23, 2014 at 09:33:45AM -0400, Michael Orlitzky wrote: |
| 2 |
> On 09/23/2014 04:54 AM, Walter Dnes wrote: |
| 3 |
> > |
| 4 |
> > Gentoo stable appears to be gcc-4.7.3-r1. ebuilds up to gcc-4.9.1 are |
| 5 |
> > present in the tree. Upgrading gcc is painful, so I appreciate the |
| 6 |
> > maintainers not forcing a rebuild with every version bump. That's the |
| 7 |
> > philosophy behind "stable". The tradeoff is that we have to wait longer |
| 8 |
> > for "new and shiney" stuff. For those who want it, you can always |
| 9 |
> > keyword a later version of gcc. |
| 10 |
> > |
| 11 |
> |
| 12 |
> Stabilization of GCC is especially careful because if your GCC winds up |
| 13 |
> broken, you might not be able to fix it (emerge won't work). |
| 14 |
> |
| 15 |
> And since GCC is used to build everything else on your system, it can't |
| 16 |
> go stable until all upstream packages are fixed or patched to work with |
| 17 |
> the new GCC. |
| 18 |
> |
| 19 |
> There's usually a tracker for those packages. For gcc-4.9 it's at, |
| 20 |
> |
| 21 |
> https://bugs.gentoo.org/show_bug.cgi?id=gcc-4.9 |
| 22 |
|
| 23 |
|
| 24 |
Since gcc is slotted (I actually have 4.7, 4.8 and 4.9 on my systems). That |
| 25 |
argument doesn't count much, imho. |
| 26 |
I personally didn't encounter a single breakage after updating from 4.8 to 4.9 |
| 27 |
(this was different from 4.7 to 4.8). |
| 28 |
IIRC 4.7 isn't supported by upstream anymore and there are known (security) |
| 29 |
bugs. I don't really know why not at least 4.8 is stable. |
Archives