-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Jerry DeLisle on 6/29/2008 11:45 AM: | Ian Lance Taylor wrote: |> CC'ed to Eric. This may require some configury patches somewhere. |> |>>>> 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. |>>> |> | A PR should be opened for this. Has that been done? Is it marked as a | regression and as a blocker?
Sorry for the delay in responding; this mail landed in my inbox while I was on vacation. An even more fundamental question (but one that still needs a PR, if you haven't created one yet) - when building libiberty on cygwin, why does it even trying to compile a strsignal replacement, since cygwin has already been providing strsignal implemented in C++ for years? ~ In other words, there should be no need to compile libiberty's strsignal.c, thus it should not matter whether you are using the 1.5.x (broken) string.h, or the 1.7.0 (fixed) prototype. | | Who has responsibility to fix this? Unfortunately, I've never compiled Fortran myself, and my experience with libiberty is very limited. I don't know why the libiberty configury isn't picking up on the fact that cygwin already has strsignal. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkh20eEACgkQ84KuGfSFAYA4NQCguIOOAziyclXoAf94fsy2VLKW uKsAnA6nfl2WMAmO81gmEpJ96mgelEHc =hsQb -----END PGP SIGNATURE-----
