From: Bart Verwilst <verwilst@gentoo.org>
To: "Matthew J. Turk" <m-turk@nwu.edu>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GCC 3.1/3.2
Date: Sun, 28 Jul 2002 12:44:45 +0200 [thread overview]
Message-ID: <200207281244.45546.verwilst@gentoo.org> (raw)
In-Reply-To: <20020728050711.GB5651@dhcp101047.res-hall.nwu.edu>
On Sunday 28 July 2002 07:07, Matthew J. Turk wrote:
|| Recently there's been some (exciting!) talk about moving to GCC 3.1 on the
|| default around the middle of August...
||
|| With the changes between 3.1 and 3.2, particularly (exclusively?) in the
|| C++ ABI, is this going to help the situation? Or are we currently
|| following the "major" distros like RedHat and Mandrake to preserve compat
|| across the spectrum of distributions?
||
|| Just curious. :)
Well, we won't be using 3.1 as default, but we'll go to 3.2 straight away..
Because 3.1 and 3.2 are incompatible again (hopefully for the last time..)
||
||
|| mjt
|| ---------------------------------------------------
|| Matthew J. Turk <m-turk@nwu.edu> ICQ: 3856787
|| "Music is the Best." - FZ thecatfishman.org
|| http://pubweb.nwu.edu/~mjt631/spamoff.htm
|| _______________________________________________
|| gentoo-dev mailing list
|| gentoo-dev@gentoo.org
|| http://lists.gentoo.org/mailman/listinfo/gentoo-dev
--
Bart Verwilst
Gentoo Linux Developer, Release Coordinator
Gent, Belgium
next prev parent reply other threads:[~2002-07-28 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 5:07 [gentoo-dev] GCC 3.1/3.2 Matthew J. Turk
2002-07-28 10:44 ` Bart Verwilst [this message]
2002-07-28 13:25 ` Doug Goldstein
2002-07-28 17:26 ` Terje Kvernes
2002-07-28 17:44 ` Matthew J. Turk
2002-07-28 18:27 ` Michael Mattsson
2002-07-28 22:16 ` Doug Goldstein
-- strict thread matches above, loose matches on Subject: below --
2002-07-28 22:01 Thomas Beaudry
2002-07-29 7:14 Michael Mattsson
2002-07-29 10:09 ` Matthew Kennedy
2002-07-29 7:28 Thomas Beaudry
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=200207281244.45546.verwilst@gentoo.org \
--to=verwilst@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=m-turk@nwu.edu \
/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