Re: [RFC] sigsetjmp/siglongjmp on cygwin

[Mark Kettenis <kettenis at wins dot uva dot nl>]

   Date: Thu, 02 Aug 2001 13:25:01 -0400
   From: Andrew Cagney <ac131313@cygnus.com>

   > Or maybe #define sigsetjmp setjmp etc., again in a Cygwin-specific
   > header.  You can even make that define be version specific, assuming
   > that some future version of Cygwin solves the problem.

   Again, I'm not too warm on this.

   Remember, the idea is for autoconf to perform a feature based test: is 
   feature XYZ supported?  In the case of the above, the feature question 
   is: does the system have a useable sigsetjmp()?  Unfortunatly, the test 
   currently asks: does the system have anything looking like sigsetjmp(), 
   working or not? :-)  I think Keith's original patch is the correct fix. 

Not quite...

It is very un-autoconf-like to use the host-triple to decide whether
things are broken or not.  If there is an easy way to check for the
broken sigsetjmp behaviour on cygwin, we really should do that instead
of relying on the host-triple.  However, I don't think we can :-(.

   It refines the test so that, for cygwin, it reports back ``no 
   sigsetjmp()'' is not there (or is broken).

Then it would be really great if configure reports back that sigsetjmp
is broken for cygwin.  Keith, I think you should set
gdb_cv_func_sigsetjmp to "broken" instead of "no" for cygwin.  With
that change your origional patch can go in.

Mark