This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: gcc 3.0.x/glibc 2.2.4 policy


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.)

-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]