From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eli Zaretskii" To: ac131313@cygnus.com Cc: keiths@cygnus.com, kettenis@science.uva.nl, gdb-patches@sources.redhat.com Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin Date: Fri, 03 Aug 2001 01:33:00 -0000 Message-id: <2110-Fri03Aug2001113257+0300-eliz@is.elta.co.il> References: <3B698CED.8030007@cygnus.com> X-SW-Source: 2001-08/msg00064.html > Date: Thu, 02 Aug 2001 13:25:01 -0400 > From: Andrew Cagney > > 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. > It refines the test so that, for cygwin, it reports back ``no > sigsetjmp()'' is not there (or is broken). Intentionally failing an Autoconf test is not my idea of using Autoconf correctly ;-) If all Cygwin wants is to fail that test unconditionally, they could simply supply a config.site file which sets the appropriate Autoconf variable (ac_cv_func_sigsetjmp, IIRC), and not bother the GDB distribution at all. After all, the same bug will bite Cygwin in any other package, right? Moreover, this problem will most probably be fixed in some future version of Cygwin, at which point someone will have to make that test know about specific Cygwin versions etc. IMHO, if we must have such an ugliness, it should go into a system-specific header.