This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Your g++ breaks glibc.
- To: hjl at varesearch dot com (H.J. Lu)
- Subject: Re: Your g++ breaks glibc.
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Thu, 15 Jul 1999 01:25:02 -0600
- cc: mark at codesourcery dot com (Mark Mitchell), jason at cygnus dot com, egcs-patches at egcs dot cygnus dot com, libc-hacker at sourceware dot cygnus dot com, bje at cygnus dot com
- Reply-To: law at cygnus dot com
In message <19990715064951.AB8803FC1@varesearch.com>you write:
> It is ncurses 4.2. However, I believe the problem is in autoconf and
> I don't even know if there is a reasonable fix for autoconf since
> it may not know which one,
I'm sure autoconf can be changed to do something reasonable. For example,
it can use a different declaration depending on what version of the compiler
is being used. Or it can try both variants to see which work.
>
> extern "C" void exit(int);
> extern "C" void exit(int) throw ();
>
> to use for a given system. gcc 2.95 works with
>
> #include <stdlib.h>
> extern "C" void exit(int);
>
> but not
>
> extern "C" void exit(int);
> #include <stdlib.h>
>
> I don't see any reason to allow one and not the other.
If the standard says one should work, but not the other, then that's a good
reason to allow one, but not the other.
jeff