old but current libiberty/strsignal vs. cygwin

[Jay]

Thanks.
I need to get back to this.
I have a workaround for now. Equiv I think to the #ifdef __CYGWIN__
in one of those threads.

I am maintaining a bunch of local patches and hope to someday get them accepted.
I had trouble building autogen, which is needed to properly patch some things.
  For example, the host vs. target mixups in the winsup directory -- try
    building -host i686-pc-cygwin -target i686-pc-mingw32; it goes and tries
    to build the cygwin/utils and cygwin/server, under the winsup directory.

The configure comment one of those mails refers to is wrong.
Cygwin stopped getting its strsignal from libiberty years ago.

However I'm not sure that code even runs.
Large swaths of configure get skipped.
I have to go check the comments in my patch.

I have to poke around here additionally to get rid of the "auto import of data" warnings.

Thanks.

Later,
 - Jay


> Date: Sun, 14 Sep 2008 10:08:22 +0200
> From: angelo.graziosi@alice.it
> To: fortran@gcc.gnu.org
> CC: aaronavay62@aaronwl.com; jay.krell@cornell.edu
> Subject: Re: old but current libiberty/strsignal vs. cygwin
>
> Aaron W. LaFramboise wrote:
>
>>> Nobody builds gcc + cygwin in an integrated tree?
>>> I wish I could integrate more into The One Tree.
>>> I so dislike everything being separate..
>>
>> Probably not, especially because relatively few people are doing their
>> own Cygwin builds at all.
>
>
> I build gfortran weekly on Cygwin! and flagged this problem on June.
>
> This thread [1] should explain many things, mainly why this problem happens.
>
>
> Cheers,
> Angelo.
>
> ---
> [1]
> http://gcc.gnu.org/ml/gcc/2008-06/msg00666.html
> http://gcc.gnu.org/ml/gcc/2008-06/msg00674.html
> http://gcc.gnu.org/ml/gcc/2008-06/msg00678.html
> http://gcc.gnu.org/ml/gcc/2008-06/msg00680.html
> http://gcc.gnu.org/ml/gcc/2008-06/msg00681.html
> http://gcc.gnu.org/ml/gcc/2008-07/msg00197.html
> http://gcc.gnu.org/ml/gcc/2008-07/msg00228.html
>
>
>
>