gcc 3.0.x/glibc 2.2.4 policy

[Andreas Jaeger]

Ulrich Drepper <drepper@redhat.com> writes:

> Andreas Jaeger <aj@suse.de> writes:
>
>> What do others think?  I don't have a problem with releasing 2.2.4 now
>> but let's agree on a plan,
>
> It's a far too big change to be included that late in the game.  It
> needs quite some time of testing and I probably still some changes.
> 2.2.4 will not have it.
>
> My plan is to apply the patch a few days after the release when it is
> hopefully clear that no stupid mistakes slipped in.  Right after the
> patch went in we'll also branch for a 2.2-stable branch to get started
> on 2.3.

This is fine with me.

Here's a patch for configure.in, what do you think?  I made this an
extra test that can be overwritten with --disable-sanity-checks.

Andreas

2001-08-09  Andreas Jaeger  <aj@suse.de>

	* configure.in: Add check for GCC 3.x.

============================================================
Index: configure.in
--- configure.in	2001/08/03 23:02:19	1.322
+++ configure.in	2001/08/09 08:24:40
@@ -636,6 +636,27 @@ test -n "$aux_missing" && AC_MSG_WARN([
 CCVERSION=`$CC -v 2>&1 | sed -n 's/gcc version //p'`
 AC_SUBST(CCVERSION)
 
+case $CCVERSION in
+  3.*) gcc3 = yes;;
+esac
+
+if test $gcc3 = yes; then
+    echo "\
+*** This version of GNU libc cannot be compiled by GCC 3.x.
+*** GCC 3.x will generate a library that is binary incompatible to
+*** older and future releases of GNU libc.
+*** You should compile this GNU libc release by an older GCC version
+*** or wait for the next GNU libc release."
+  if test $enable_sanity = yes; then
+    echo "\
+*** If you really mean to use GCC 3.x, run configure again
+*** using the extra parameter \`--disable-sanity-checks'."
+    exit 1
+  else
+    echo "\
+*** This configuration is not supported by the GNU libc developers."
+  fi
+fi
 # if using special system headers, find out the compiler's sekrit
 # header directory and add that to the list.  NOTE: Only does the right
 # thing on a system that doesn't need fixincludes.  (Not presently a problem.)

-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7ckkAOJpWPMJyoSYRAq1SAJ98jeBU/8hqIhRTENCA3rQjKDLS5gCfYoPl
6oj7YHOu7DzCG/ooIVarq5w=
=8YYp
-----END PGP SIGNATURE-----From drepper@redhat.com Thu Aug 09 01:29:00 2001
From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: Re: gcc 3.0.x/glibc 2.2.4 policy
Date: Thu, 09 Aug 2001 01:29:00 -0000
Message-id: <m3k80d63qn.fsf@otr.mynet>
References: <hod768dxvq.fsf@gee.suse.de> <m3zo9bzt5t.fsf@otr.mynet> <hod7651vy8.fsf@gee.suse.de>
X-SW-Source: 2001-08/msg00031.html
Content-length: 453

Andreas Jaeger <aj@suse.de> writes:

> Here's a patch for configure.in, what do you think?  I made this an
> extra test that can be overwritten with --disable-sanity-checks.

Looks good.  I assume you tested it?  If yes, go ahead.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------