On Thu, Nov 11, 2010 at 10:34 PM, Ryan Hill <dirtye...@gentoo.org> wrote: > On Thu, 11 Nov 2010 20:37:51 -0500 > Matt Turner <matts...@gentoo.org> wrote: > >> On Thu, Nov 11, 2010 at 8:28 PM, Ryan Hill <dirtye...@gentoo.org> wrote: >> > On Thu, 11 Nov 2010 18:00:00 -0500 >> > Matt Turner <matts...@gentoo.org> wrote: >> > >> >> Should we target package versions that aren't stabilized on other >> >> architectures yet, so that we'll have an extended testing period >> >> before they'll come up for stabilization? That is, can I plan to make >> >> gcc-4.5.1 or something the first restabilized version of gcc, go ahead >> >> and begin testing it, and be ready for stabilization when toolchain >> >> requests it? >> > >> > I'd work on getting it ~mips before you think about stabilizing. ;) Last >> > report I got it doesn't build. >> >> I've been using gcc-4.5.1 for the last two weeks or so. :) >> >> Should I add a ~mips keyword? > > Kumba told me about some weird behavior he saw where the stage 2 and 3 > comparison failed and the build restarted from scratch again and got into an > endless loop. Maybe a hardware problem?
I talked with him on IRC last night and he's fine with adding ~mips. No idea what's the deal with his box. > If you want to keyword 4.5.1 then you'll need to keyword dev-libs/mpc (bug > #279851) and either keyword dev-libs/cloog-ppl or mask the graphite USE flag > in your profiles (bug #269088). Keyworded mpc-0.8.2, cloog-ppl-0.15.9, and gcc-4.5.1. Please check to make sure I didn't screw anything up. I'm new at this you know. :) Thanks, Matt