This is the mail archive of the
glibc-linux@ricardo.ecn.wfu.edu
mailing list for the glibc project.
glibc-2.2.4 and gcc-3.0 ?
- To: glibc-linux at ricardo dot ecn dot wfu dot edu
- Subject: glibc-2.2.4 and gcc-3.0 ?
- From: Urs Thuermann <urs at isnogud dot escape dot de>
- Date: 20 Aug 2001 15:57:19 +0200
- Reply-To: glibc-linux at ricardo dot ecn dot wfu dot edu
When configuring glibc-2.2.4 unsing gcc-3.0 I get the message
*** 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 you really mean to use GCC 3.x, run configure again
*** using the extra parameter `--disable-sanity-checks'.
I have searched the FAQ and other docs, but couldn't any info on this.
* What does gcc-3.0 do so differently that it generates a binary
incompatible library? Does that mean that my system wouldn't work,
if I compiled glibc-2.2.4 with gcc-3.0 and install it in place of
the currently installd glibc-2.2.3, which I have compiled with
gcc-2.95.3?
* What does --disable-sanity-checks do? This seems to be
undocumentend.
* When will the next GNU libc release be available that can be
compiled with gcc-3.x?
* Would glibc-2.2.3 compiled with gcc-3.0 have the same problem? At
least the configure script does not complain about gcc-3.0.
urs