Failure building GFortran (Cygwin)

Angelo Graziosi angelo.graziosi@alice.it
Sun Jun 29 16:00:00 GMT 2008


The point isn't that to find workarounds.

The point is, so as stand the things, unless a new Cygwin 1.5.25-16 (or 
1.5.26-1 ?), the build of GFortran-trunk and friends is *officially* 
broken for cygwin-users.


Thanks,
    Angelo.


Dave Korn ha scritto:
> Angelo Graziosi wrote on 29 June 2008 11:38:
> 
>> Oops, I have discovered this, in libiberty/ChangeLog
>>
>> 2008-06-19  Eric Blake  <xxx@xxxx>
>>
>> 	Adjust strsignal to POSIX 200x prototype.
>> 	* strsignal.c (strsignal): Remove const.
> 
>   You may need to build and install cygwin from CVS[*] to get the
> corresponding newlib fix and install it into your system headers in
> /usr/include.  Or you could patch your /usr/include/string.h locally.  See
> 
> http://sourceware.org/ml/newlib/2008/msg00342.html
> 
> for the other half of Eric's patch.
> 
>     cheers,
>       DaveK
> 
> [*] - You may not want to do that because of the 1.5 -> 1.7 WIP, in which
> case you could rebuild your current DLL from its source package and backport
> the patch linked above.



More information about the Gcc mailing list