Current stable in the 4.3 slot does not build, we should have a new stable. Any objections? If not, please add arches. Thanks.
No objections. In fact I suggested exactly this in one of the stabilization discussions in one of the bugs (cannot find it now - too slow internet to do anything usefull :(. I am on the go right now and until the end of the month). Actually, the stabilization bugs were mostly concerning the 4.4 series IIRC, so it could be among those. 4.3.5 should work on at least x86 and amd64. I am afraid I fell behind on ppc and sparc (where applicable 4.3/4.4-wise), but then I do not have access to these arches and have to rely on users to build me a tarball which I repackage. I'll get back to updating the bootstraps when I get back, OTOH I will need to finish some grants and papers first I am afraid as well. So, somewhere mid-Sept I'd guess. I'll add arches appropriately to CC when I figure out the exact situation with all the versions, but if you are from one of the arches and want to push for it, 4.3.5 should be good for x86 and amd64 right now.
(In reply to comment #1) > No objections. In fact I suggested exactly this in one of the stabilization > discussions in one of the bugs (cannot find it now - too slow internet to do > anything usefull :(. I am on the go right now and until the end of the month). > Actually, the stabilization bugs were mostly concerning the 4.4 series IIRC, so > it could be among those. > > 4.3.5 should work on at least x86 and amd64. I am afraid I fell behind on ppc > and sparc (where applicable 4.3/4.4-wise), but then I do not have access to > these arches and have to rely on users to build me a tarball which I repackage. > I'll get back to updating the bootstraps when I get back, OTOH I will need to > finish some grants and papers first I am afraid as well. So, somewhere mid-Sept > I'd guess. I'll add arches appropriately to CC when I figure out the exact > situation with all the versions, but if you are from one of the arches and want > to push for it, 4.3.5 should be good for x86 and amd64 right now. Thanks for the update. Funnily 4.3.5 worked on one machine and failed on another with the -march trouble. Both have the same -march=core2 setting... This is weird! However, 4.3.5 is not worse than 4.3.2 so I will stable it together with alpine. It would be great if you could stable a 4.4 version soon, at least for x86 and amd64. Thanks.
Just added 4.3.6 with a new bootstrap, closing the -march and mpfr issues (what has been done for 4.4 a while ago). amd64 only atm (new ebuild, to accomodate bootstrap specific changes). Will add x86 right next. It would make sense to stabilize this one, as well. It is certainly no worse than 4.3.5. Stabling 4.4.5 or both of these would be even better.
4.3.5 is stable on all arches that have any stable gnat, think this can be closed (or updated to be about 4.4.x)
(In reply to comment #4) > 4.3.5 is stable on all arches that have any stable gnat, think this can be > closed (or updated to be about 4.4.x) That is not true `equery meta gnat-gcc` * dev-lang/gnat-gcc [gentoo] Herd: ada (ada@gentoo.org) Maintainer: None specified Upstream: None specified Homepage: http://gcc.gnu.org/ Location: /usr/portage/dev-lang/gnat-gcc Keywords: 3.4.6:3.4: amd64 x86 Keywords: 4.1.2:4.1: amd64 x86 ~ppc Keywords: 4.2.3:4.2: amd64 ppc x86 Keywords: 4.3.2:4.3: ppc Keywords: 4.3.3:4.3: ~ppc Keywords: 4.3.5:4.3: amd64 x86 ~sparc Keywords: 4.3.6:4.3: ~amd64 ~x86 Keywords: 4.4.3:4.4: Keywords: 4.4.5:4.4: ~amd64 ~sparc ~x86
I see: equery meta gnat-gcc * dev-lang/gnat-gcc [gentoo] Herd: ada (ada@gentoo.org) Maintainer: None specified Upstream: None specified Homepage: http://gcc.gnu.org/ Location: /usr/portage/dev-lang/gnat-gcc Keywords: 3.4.6:3.4: amd64 x86 Keywords: 4.1.2:4.1: amd64 x86 ~ppc Keywords: 4.2.3:4.2: amd64 ppc x86 Keywords: 4.3.5:4.3: amd64 x86 ~sparc Keywords: 4.3.6:4.3: ~amd64 ~ppc ~x86 Keywords: 4.4.3:4.4: Keywords: 4.4.5:4.4: Keywords: 4.4.7:4.4: ~amd64 ~sparc ~x86 Keywords: 4.5.4:4.5: ~amd64 ~sparc ~x86 Keywords: 4.6.4:4.6: ~amd64 ~sparc ~x86 I guess the idea would be to stabilize latest version per slot then?
This is needed for texinfo too -> bug 468108
Arches please test and stabilize: =dev-lang/gnat-gcc-4.3.6 amd64 ppc x86 =dev-lang/gnat-gcc-4.4.7 amd64 x86 =dev-lang/gnat-gcc-4.5.4 amd64 x86 =dev-lang/gnat-gcc-4.6.4 amd64 x86
x86 and amd64 is enough for 4.3.x
and 4.4 slot looks to be completely broken, do the rest then
amd64/x86 stable
