public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GCC 4.1.1 testing/stablization and glibc 2.4
Date: Tue, 27 Jun 2006 20:20:35 -0400	[thread overview]
Message-ID: <200606272020.35407.vapier@gentoo.org> (raw)
In-Reply-To: <44A1B1E8.4020202@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

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

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2006-06-28  0:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 21:56 [gentoo-dev] GCC 4.1.1 testing/stablization and glibc 2.4 Chris Gianelloni
2006-06-27 22:32 ` Donnie Berkholz
2006-06-28  0:20   ` Mike Frysinger [this message]
2006-06-27 22:33 ` Dan Meltzer
2006-07-01 18:18 ` [gentoo-dev] " Ryan Hill
2006-07-02 14:13   ` Chris Gianelloni
2006-07-16  1:33     ` Ryan Hill
2006-07-16 22:06       ` Ryan Hill
2006-07-16  6:06     ` R Hill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200606272020.35407.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox