Re: libiberty strsignal changes cause windows compilation breakage

[Chris Faylor <cgf at cygnus dot com>]

On Thu, Jun 01, 2000 at 02:04:31AM -0400, Eli Zaretskii wrote:
>> From: Chris Faylor <cgf@cygnus.com>
>> Date: Wed, 31 May 2000 18:29:10 -0400
>> 
>> The strsignal file in libiberty was recently updated to include
>> "string.h".  This has an unpleasant side effect on cygwin in that the
>> declaration for strsignal in newlib's string.h is essentially this:
>> 
>> char *strsignal (int sig);
>> 
>> while the definition in strsignal.c is:
>> 
>> const char *strsignal (int sig)
>
>If the Cygwin library has strsignal (which, as I understand, is the
>reason for the prototype in string.h), then why is libiberty's
>strsignal being linked in?  Shouldn't the configure script detect that
>and refrain from using libiberty's strsignal?

I think you missed this part of my email:

>This is interesting since cygwin's version of strsignal comes from
>libiberty.

"comes from" == "linked from"

The cygwin DLL exports libiberty's version of strsignal.

cgf