This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] sigsetjmp/siglongjmp on cygwin
- To: ac131313 at cygnus dot com
- Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- Date: Fri, 03 Aug 2001 11:32:57 +0300
- CC: keiths at cygnus dot com, kettenis at science dot uva dot nl, gdb-patches at sources dot redhat dot com
- References: <Pine.SUN.3.91.1010802095808.28510L-100000@is> <3B698CED.8030007@cygnus.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Thu, 02 Aug 2001 13:25:01 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
>
> 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.