Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Gentoo>
  3. Dev
GCC 4.1.1 testing/stablization and glibc 2.4
wolf31o2 at gentoo
Jun 27, 2006, 2:56 PM
Post #1 of 9 (200 views)
Permalink
OK, guys, I was speaking with vapier earlier about the possibility of
getting gcc 4.1.1 stable for the 2006.1 release. We've managed to build
some release media with it, and are planning on doing more testing with
it. What we really need is for more people to test this on various
platforms and to get all of the bugs worked out that we can. We're
already ramping up our release cycle, and would like to get this
included, so we don't have to wait until 2007 for a release with >= GCC
4.1 in it.

We are also testing glibc 2.4, which will likely go to stable on the
supporting architectures during the release cycle. We always welcome
more testing, though. =]

--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

Attached Files:

Re: GCC 4.1.1 testing/stablization and glibc 2.4 [ In reply to ]
spyderous at gentoo
Jun 27, 2006, 3:32 PM
Post #2 of 9 (202 views)
Permalink
Chris Gianelloni wrote:
> OK, guys, I was speaking with vapier earlier about the possibility of
> getting gcc 4.1.1 stable for the 2006.1 release. We've managed to build
> some release media with it, and are planning on doing more testing with
> it. What we really need is for more people to test this on various
> platforms and to get all of the bugs worked out that we can. We're
> already ramping up our release cycle, and would like to get this
> included, so we don't have to wait until 2007 for a release with >= GCC
> 4.1 in it.

That would be really cool. I'm already been testing both this and the
glibc on the ~1500 packages installed on my x86, plus the Pegasos ppc
and iBook I've got around. I'll do the same on sparc as soon as it shows
up in ~arch there.

> We are also testing glibc 2.4, which will likely go to stable on the
> supporting architectures during the release cycle. We always welcome
> more testing, though. =]

Thanks,
Donnie

Attached Files:

Re: GCC 4.1.1 testing/stablization and glibc 2.4 [ In reply to ]
parallelgrapefruit at gmail
Jun 27, 2006, 3:33 PM
Post #3 of 9 (199 views)
Permalink
On 6/27/06, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> OK, guys, I was speaking with vapier earlier about the possibility of
> getting gcc 4.1.1 stable for the 2006.1 release. We've managed to build
> some release media with it, and are planning on doing more testing with
> it. What we really need is for more people to test this on various
> platforms and to get all of the bugs worked out that we can. We're
> already ramping up our release cycle, and would like to get this
> included, so we don't have to wait until 2007 for a release with >= GCC
> 4.1 in it.
>
> We are also testing glibc 2.4, which will likely go to stable on the
> supporting architectures during the release cycle. We always welcome
> more testing, though. =]
>
I've been running gcc-4.1.1 and glibc-2.4-r3 for a while now and have
seen no problems running or compiling anything with them yet on x86.
> --
> Chris Gianelloni
> Release Engineering - Strategic Lead
> x86 Architecture Team
> Games - Developer
> Gentoo Linux
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQBEoal/kT4lNIS36YERAjYkAJ0dsk34qihWGSPATm/fj/qpYg+euACeOzh+
> Rc6nW515lcQ0KXewJ1q1J/o=
> =DiU1
> -----END PGP SIGNATURE-----
>
>
>
--
gentoo-dev@gentoo.org mailing list
Re: GCC 4.1.1 testing/stablization and glibc 2.4 [ In reply to ]
vapier at gentoo
Jun 27, 2006, 5:20 PM
Post #4 of 9 (198 views)
Permalink
On Tuesday 27 June 2006 18:32, Donnie Berkholz wrote:
> Chris Gianelloni wrote:
> > OK, guys, I was speaking with vapier earlier about the possibility of
> > getting gcc 4.1.1 stable for the 2006.1 release. We've managed to build
> > some release media with it, and are planning on doing more testing with
> > it. What we really need is for more people to test this on various
> > platforms and to get all of the bugs worked out that we can. We're
> > already ramping up our release cycle, and would like to get this
> > included, so we don't have to wait until 2007 for a release with >= GCC
> > 4.1 in it.
>
> That would be really cool. I'm already been testing both this and the
> glibc on the ~1500 packages installed on my x86, plus the Pegasos ppc
> and iBook I've got around. I'll do the same on sparc as soon as it shows
> up in ~arch there.

the trouble is we need these packages in arch now, not ~arch :)
-mike
Re: Re: GCC 4.1.1 testing/stablization and glibc 2.4 [ In reply to ]
wolf31o2 at gentoo
Jul 2, 2006, 7:13 AM
Post #5 of 9 (200 views)
Permalink
On Sat, 2006-07-01 at 12:18 -0600, Ryan Hill wrote:
> Chris Gianelloni wrote:
> > OK, guys, I was speaking with vapier earlier about the possibility of
> > getting gcc 4.1.1 stable for the 2006.1 release. We've managed to build
> > some release media with it, and are planning on doing more testing with
> > it. What we really need is for more people to test this on various
> > platforms and to get all of the bugs worked out that we can. We're
> > already ramping up our release cycle, and would like to get this
> > included, so we don't have to wait until 2007 for a release with >= GCC
> > 4.1 in it.
>
> Should arch testers start working with 4.1.1 then? And do you want bugs to
> block #117482?

Arch testers should contact their architecture's leads or Release
Engineering Architecture Coordinator. As for bug reports, yes.

--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

Attached Files:

Re: GCC 4.1.1 testing/stablization and glibc 2.4 [ In reply to ]
dirtyepic.sk at gmail
Jul 15, 2006, 11:06 PM
Post #6 of 9 (194 views)
Permalink
(apologies in advance if this goes through twice)

Chris Gianelloni wrote:
> On Sat, 2006-07-01 at 12:18 -0600, Ryan Hill wrote:

>> Should arch testers start working with 4.1.1 then? And do you want bugs to
>> block #117482?

> Arch testers should contact their architecture's leads or Release
> Engineering Architecture Coordinator. As for bug reports, yes.

Just an update - I've finished most major desktop stuff for x86 without any
problems. I'm moving onto stuff that's already on the tracker and is fixed in
testing but not stable. Rather than open and track a ton of new bugs, I'd like
to reopen the original ~arch bugs and request a backport or stabilization at the
maintainer's discretion.

Is this okay, or would people rather get a shiny new bug? Keep in mind there
are already 290 bugs on the tracker. Alternatively, would it be better to just
start a new tracker bug for stabilization?

https://bugs.gentoo.org/show_bug.cgi?id=117482

--de.


--
gentoo-dev@gentoo.org mailing list
Re: GCC 4.1.1 testing/stablization and glibc 2.4 [ In reply to ]
dirtyepic.sk at gmail
Jun 17, 2008, 1:07 AM
Post #7 of 9 (198 views)
Permalink
Chris Gianelloni wrote:
> OK, guys, I was speaking with vapier earlier about the possibility of
> getting gcc 4.1.1 stable for the 2006.1 release. We've managed to build
> some release media with it, and are planning on doing more testing with
> it. What we really need is for more people to test this on various
> platforms and to get all of the bugs worked out that we can. We're
> already ramping up our release cycle, and would like to get this
> included, so we don't have to wait until 2007 for a release with >= GCC
> 4.1 in it.

Should arch testers start working with 4.1.1 then? And do you want bugs to
block #117482?

--de.


https://bugs.gentoo.org/show_bug.cgi?id=117482

Attached Files:

Re: GCC 4.1.1 testing/stablization and glibc 2.4 [ In reply to ]
dirtyepic.sk at gmail
Jun 17, 2008, 1:08 AM
Post #8 of 9 (196 views)
Permalink
Chris Gianelloni wrote:
> On Sat, 2006-07-01 at 12:18 -0600, Ryan Hill wrote:

>> Should arch testers start working with 4.1.1 then? And do you want bugs to
>> block #117482?

> Arch testers should contact their architecture's leads or Release
> Engineering Architecture Coordinator. As for bug reports, yes.

Just an update - I've finished most major desktop stuff for x86 without any
problems. I'm moving onto stuff that's already on the tracker and is fixed in
testing but not stable. Rather than open and track a ton of new bugs, I'd like
to reopen the original ~arch bugs and request a backport or stabilization at the
maintainer's discretion.

Is this okay, or would people rather get a shiny new bug? Keep in mind there
are already 290 bugs on the tracker. Alternatively, would it be better to just
start a new tracker bug for stabilization?

https://bugs.gentoo.org/show_bug.cgi?id=117482

--de.

Attached Files:

Re: GCC 4.1.1 testing/stablization and glibc 2.4 [ In reply to ]
dirtyepic.sk at gmail
Jun 17, 2008, 1:08 AM
Post #9 of 9 (197 views)
Permalink
Ryan Hill wrote:

> Just an update - I've finished most major desktop stuff for x86 without any
> problems. I'm moving onto stuff that's already on the tracker and is fixed in
> testing but not stable. Rather than open and track a ton of new bugs, I'd like
> to reopen the original ~arch bugs and request a backport or stabilization at the
> maintainer's discretion.

I changed my mind. Reopening these just creates too much random bugspam.

--de.

Attached Files:

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal