[Python-Dev] forwarded message from Gerald Pfeifer
Fred L. Drake, Jr.
Thu, 5 Oct 2000 20:14:20 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Content-Description: message body and .signature
I just got this message from the gcc-announce list. We've seen bug
reports related to GCC 2.96 (which may or may not be the problem). We
need to be aware that these releases are out there and can be a
I've noticed that the version of GCC shipped with Mandrake 7.1 is
"gcc version 2.95.3 19991030 (prerelease)", which doesn't give my much
confidence either. ;(
Fred L. Drake, Jr. <fdrake at beopen.com>
BeOpen PythonLabs Team Member
Content-Description: forwarded message
Received: by ns1.beopen.com (mbox fdrake)
(with Cubic Circle's cucipop (v1.31 1998/05/13) Thu Oct 5 17:12:18 2000)
X-From_: email@example.com Thu Oct 5 17:07:40 2000
Received: from mail.acm.org (mail.acm.org [220.127.116.11])
by ns1.beopen.com (8.9.3/8.9.3) with ESMTP id RAA90031
for <firstname.lastname@example.org>; Thu, 5 Oct 2000 17:07:39 -0700 (PDT)
Received: from sourceware.cygnus.com (sourceware.cygnus.com [18.104.22.168])
by mail.acm.org (8.9.3/8.9.3) with SMTP id UAA45682
for <email@example.com>; Thu, 5 Oct 2000 20:05:32 -0400
Received: (qmail 23247 invoked by alias); 6 Oct 2000 00:03:53 -0000
Mailing-List: contact firstname.lastname@example.org; run by ezmlm
Delivered-To: mailing list email@example.com
Delivered-To: moderator for firstname.lastname@example.org
Received: (qmail 20621 invoked from network); 5 Oct 2000 23:58:16 -0000
Content-Type: TEXT/PLAIN; charset=US-ASCII
From: Gerald Pfeifer <email@example.com>
Subject: GCC 2.96
Date: Fri, 6 Oct 2000 01:58:11 +0200 (CEST)
It has come to our attention that some GNU/Linux distributions are
currently shipping with ``GCC 2.96''.
We would like to point out that GCC 2.96 is not a formal GCC release nor
will there ever be such a release. Rather, GCC 2.96 has been the code-
name for our development branch that will eventually become GCC 3.0.
Current snapshots of GCC, and any version labeled 2.96, produce object
files that are not compatible with those produced by either GCC 2.95.2 or
the forthcoming GCC 3.0. Therefore, programs built with these snapshots
will not be compatible with any official GCC release. Actually, C and
Fortran code will probably be compatible, but code in other languages,
most notably C++ due to incompatibilities in symbol encoding (``mangling''),
the standard library and the application binary interface (ABI), is likely
to fail in some way. Static linking against C++ libraries may make a
binary more portable, at the cost of increasing file size and memory use.
To avoid any confusion, we have bumped the version of our current
development branch to GCC 2.97.
Please note that both GCC 2.96 and 2.97 are development versions; we
do not recommend using them for production purposes. Binaries built
using any version of GCC 2.96 or 2.97 will not be portable to systems
based on one of our regular releases.
If you encounter a bug in a compiler labeled 2.96, we suggest you
contact whoever supplied the compiler as we can not support 2.96
versions that were not issued by the GCC team.
Please see http://gcc.gnu.org/snapshots.html if you want to use our
latest snapshots. We suggest you use 2.95.2 if you are uncertain.
The GCC Steering Committee <http://gcc.gnu.org/steering.html>