public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Faulhammer <opfer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: GCC 4.3 pre-stabilization
Date: Sat, 1 Nov 2008 14:30:09 +0100	[thread overview]
Message-ID: <20081101143009.7f506d2e@terra.solaris> (raw)
In-Reply-To: <20081031122846.69eb3b20@halo.dirtyepic.sk.ca>

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

Hi,

Ryan Hill <dirtyepic@gentoo.org>:

> In anticipation of getting GCC 4.3 stabilized sometime, I'd like to
> ask maintainers check if their current stable packages build with
> 4.3, and if not please stabilize a version that does in the near
> future if at all possible.  Stabilizing this version is going to be a
> huge job due to the number of packages that don't compile due to
> implicit C++ standard library header dependencies that got cleaned up
> in 4.3.[i], so anything you could do ahead of time to save our sanity
> would be greatly appreciated.

 Is there a bug that is blocked by such stabilisation requests?  We had
such a thing on the GCC 4 transition (apart from the normal porting
tracker) and was really handy.  I will rebuild three x86 systems (one
totally stable, two mostly) to check.

V-Li

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://www.faulhammer.org/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-11-01 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 18:28 [gentoo-dev] GCC 4.3 pre-stabilization Ryan Hill
2008-11-01 13:30 ` Christian Faulhammer [this message]
2008-11-01 17:22   ` [gentoo-dev] " Ryan Hill
2008-11-01 17:30 ` [gentoo-dev] " Jose Luis Rivero
2008-11-01 22:29   ` [gentoo-dev] " Ryan 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=20081101143009.7f506d2e@terra.solaris \
    --to=opfer@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