This is the mail archive of the
mailing list for the GCC project.
Re: libiberty/strsignal.c decl breaks with old Cygwin tool-chains
- To: Alexandre Oliva <aoliva at redhat dot com>
- Subject: Re: libiberty/strsignal.c decl breaks with old Cygwin tool-chains
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 06 Sep 2000 20:58:59 -0600
- cc: gcc-patches at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <email@example.com>you write:
> When building a Canadian cross for Cygwin using an older Cygwin
> tool-chain, we often get this problem because the prototype of
> strsignal changed. This patch fixes the problem. Ok to install?
> Content-Type: text/x-patch
> Content-Disposition: inline; filename=liberty-strsignal-cygwin.patch
> Index: libiberty/ChangeLog
> from Alexandre Oliva <firstname.lastname@example.org>
> * strsignal.c (strsignal): Remove the `const' from the return
> value when building with old Cygwin tool-chains.
Hmmm, where is the bogus prototype for strsignal coming from? I doubt
it's coming from GCC itself, which makes me thing that testing for a
particular version of GCC is the wrong thing to do.
In fact, it seems to me that we should be checking for the bogon using
autoconf. Or am I missing something important here?