Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
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	[thread overview]
Message-ID: <2110-Fri03Aug2001113257+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3B698CED.8030007@cygnus.com>

> 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.


  parent reply	other threads:[~2001-08-03  1:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01 14:01 Keith Seitz
     [not found] ` <s3iae1jjso2.fsf@soliton.wins.uva.nl>
2001-08-01 16:03   ` Keith Seitz
2001-08-01 23:57     ` Eli Zaretskii
2001-08-02 10:25       ` Andrew Cagney
2001-08-02 13:15         ` Mark Kettenis
2001-08-13 14:46           ` Jim Blandy
2001-08-13 15:12             ` Keith Seitz
2001-08-13 15:37               ` Andrew Cagney
2001-08-13 15:43                 ` Keith Seitz
2001-08-13 15:52                   ` Andrew Cagney
2001-08-13 16:27                     ` Keith Seitz
2001-08-13 16:32                       ` Christopher Faylor
     [not found]                         ` <20010813222037.A20589@redhat.com>
2001-08-13 19:40                           ` [RFC] sigsetjmp/siglongjmp on cygwin -- problem tracked down Andrew Cagney
2001-08-13 19:55                             ` Christopher Faylor
2001-08-13 20:10                               ` Daniel Jacobowitz
2001-08-13 20:18                                 ` [RFA] work around sigsetjmp/siglongjmp macro problems Christopher Faylor
2001-08-14  0:06                                   ` Eli Zaretskii
2001-08-14  7:40                                     ` Christopher Faylor
2001-08-14  9:34                                   ` Keith Seitz
2001-08-14 13:01                                     ` Elena Zannoni
2001-08-14 13:08                                       ` Christopher Faylor
2001-08-14 23:52                                         ` Eli Zaretskii
2001-08-14 23:49                                       ` Eli Zaretskii
2001-08-13 17:11                       ` [RFC] sigsetjmp/siglongjmp on cygwin Andrew Cagney
2001-08-13 17:23                         ` Keith Seitz
2001-08-03  1:33         ` Eli Zaretskii [this message]
2001-08-10  0:16           ` Andrew Cagney
2001-08-01 16:16   ` Andrew Cagney
2001-08-02 13:51     ` Christopher Faylor
2001-08-10  0:27 ` Andrew Cagney
2001-08-12 15:49   ` Ben Elliston
2001-08-13  2:03     ` Eli Zaretskii
2001-08-13 15:42       ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2110-Fri03Aug2001113257+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=keiths@cygnus.com \
    --cc=kettenis@science.uva.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox