| 1 |
On Thursday 10 April 2008, Mike Frysinger wrote: |
| 2 |
> gcc-4.3 seems to be standing up well. since the major gcc-ebuild-specific |
| 3 |
> issues seem to be resolved now, i'll probably do a sweep of bugs to see if |
| 4 |
> there's any patches i'm missing (if you guys know of a bug that should be |
| 5 |
> addressed specifically in the gcc-4.3.0 ebuild, speak up now). |
| 6 |
> |
| 7 |
> then move on to the gcc 4.3 tracker bug (#198121). once this gets below a |
| 8 |
> certain critical mass (i wont know what the critical mass is until it's |
| 9 |
> been de-attained), then we'll be ~arching things. people are recommended |
| 10 |
> to do a quick sweep of the lower hangers (many bugs have simple patches). |
| 11 |
> |
| 12 |
> i'll drop in ~ppc ~amd64 ~x86 as i use those every day. if any other arch |
| 13 |
> is happy now with things, add your ~arch to the commented out list in cvs |
| 14 |
> so i know to include it. |
| 15 |
|
| 16 |
the x86 cld revert is in now as well as some more upstream pr fixes. i'll |
| 17 |
probably let things settle for this week and pending any craziness, move |
| 18 |
gcc-4.3.0-r1 into ~arch in a week. i'll prob commit some "obvious" gcc-4.3 |
| 19 |
bugs at the same time. |
| 20 |
|
| 21 |
last chance to speak up peeps. |
| 22 |
-mike |
Archives