From: Mark Loeser <halcy0n@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Moving GCC-3.4 to stable on x86
Date: Mon, 28 Nov 2005 09:22:33 -0500 [thread overview]
Message-ID: <20051128142233.GA19195@aerie.halcy0n.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
This is basically a heads-up email to everyone to say that we are probably
going to be moving gcc-3.4.4-r1 to stable on x86 very soon. If any of the
archs that have already done the move from having 3.3 stable to 3.4 could
give us a heads up on what to expect, that would be great. Only thing I see
as lacking is we might want to get a doc together on how to properly upgrade
your toolchain so we don't get an influx of bugs from users that have a
system half compiled with 3.3 and the other half with 3.4 so they get linking
errors.
Thanks,
Mark
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-11-28 14:25 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 14:22 Mark Loeser [this message]
2005-11-28 14:46 ` [gentoo-dev] Moving GCC-3.4 to stable on x86 Mike Frysinger
2005-11-28 18:12 ` Bjarke Istrup Pedersen
2005-11-28 22:24 ` Daniel Gryniewicz
2005-11-28 23:11 ` [gentoo-dev] " R Hill
2005-11-29 2:30 ` [gentoo-dev] " Mike Frysinger
2005-11-29 2:40 ` Mark Loeser
2005-11-29 8:51 ` Gregorio Guidi
2005-11-29 9:04 ` Paul de Vrieze
2005-11-29 9:53 ` Graham Murray
2005-11-29 10:09 ` Paul de Vrieze
2005-11-29 14:50 ` Chris Gianelloni
2005-11-29 15:03 ` Mike Frysinger
2005-11-29 15:42 ` Chris Gianelloni
2005-11-29 15:52 ` Chris Gianelloni
2005-11-29 16:04 ` Mike Frysinger
2005-11-29 17:37 ` Andreas Proschofsky
2005-11-29 18:26 ` Chris Gianelloni
2005-12-01 17:26 ` Paul Varner
2005-11-29 16:51 ` Peter Ruskin
2005-11-29 8:56 ` Paul de Vrieze
2005-11-29 11:18 ` Henrik Brix Andersen
2005-11-29 13:18 ` Paul de Vrieze
2005-11-29 13:21 ` Mark Loeser
2005-11-29 13:50 ` Curtis Napier
2005-11-29 14:03 ` William Kenworthy
2005-11-29 16:38 ` Tres Melton
2005-11-29 15:50 ` Henrik Brix Andersen
2005-11-29 15:01 ` Mike Williams
2005-11-29 15:39 ` Chris Gianelloni
2005-11-30 4:41 ` Andrew Muraco
2005-11-30 14:06 ` Chris Gianelloni
2005-11-30 14:16 ` tuxp3
2005-11-30 14:25 ` Mike Frysinger
2005-11-30 14:45 ` Graham Murray
2005-11-30 18:56 ` Mark Loeser
2005-11-30 19:25 ` Petteri Räty
2005-11-30 20:00 ` Wernfried Haas
2005-11-30 20:07 ` Andrew Muraco
2005-11-30 20:12 ` Mark Loeser
2005-11-30 20:16 ` Andrew Muraco
2005-11-30 20:51 ` Georgi Georgiev
2005-11-30 21:13 ` Andrew Muraco
2005-11-30 21:19 ` Mark Loeser
2005-12-01 4:41 ` Lares Moreau
2005-12-01 5:17 ` [gentoo-dev] " R Hill
2005-12-01 11:50 ` Jason Wever
2005-12-01 12:47 ` Chris Gianelloni
2005-12-01 14:33 ` Lares Moreau
2005-11-30 21:19 ` [gentoo-dev] " Peter Ruskin
2005-11-30 21:27 ` Re[2]: " Jakub Moc
2005-11-30 22:15 ` Peter Ruskin
2005-11-30 22:48 ` Harald van Dijk
2005-11-30 21:31 ` Simon Strandman
2005-11-30 22:34 ` Philip Webb
2005-11-30 22:42 ` Ciaran McCreesh
2005-11-30 22:43 ` Grant Goodyear
2005-11-30 22:48 ` Mark Loeser
2005-11-30 23:29 ` Chris Gianelloni
2005-11-30 23:41 ` Re[2]: " Jakub Moc
2005-11-30 23:50 ` Mark Loeser
2005-12-01 0:30 ` Marien Zwart
2005-12-01 0:53 ` Re[2]: " Jakub Moc
2005-12-01 1:07 ` Marien Zwart
2005-12-02 2:03 ` Matthias Langer
2005-12-02 2:14 ` Matthias Langer
2005-12-01 1:19 ` Philip Webb
2005-12-01 9:19 ` Petteri Räty
2005-11-30 21:34 ` solar
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=20051128142233.GA19195@aerie.halcy0n.com \
--to=halcy0n@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