Re: [RFC] sigsetjmp/siglongjmp on cygwin

[Jim Blandy <jimb at zwingli dot cygnus dot com>]

Mark Kettenis <kettenis@wins.uva.nl> writes:
> 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 :-(.

I'd like to weigh in on Mark's side here.

I did the conversion of GNU Emacs from old-style configuration, with a
header file describing each host, to autoconf-style configuration.
The difference is pretty dramatic.  Updating and fixing header files
used to be a pretty constant background activity; after switching to
autoconf, it just wasn't a big deal any more.

I would always recommend adding a "does this work?" test to
configure.in over statically associating an answer with a particular
host, whether via a per-host header file, or via a case statement
switching on the host triple.  They're really not that hard to write.

Keith Seitz writes:
> I hate touching configure.in: it makes everyone recompile all of
> gdb.

My heart bleeds.  :)  The world can handle another coffee break.