X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Wed, 14 Nov 2007 14:46:49 +0100
From:	=?iso-8859-1?Q?Joaqu=EDn=20M=AA=20L=F3pez=20Mu=F1oz?= <joaquin AT tid DOT es>
Subject:	Re: Support for sa_sigaction
To:	cygwin AT cygwin DOT com
Message-id:	<473AFC49.F8152857@tid.es>
MIME-version:	1.0
X-Mailer:	Mozilla 4.78 [es] (Windows NT 5.0; U)
References:	<473AC8C0 DOT 22E4822B AT tid DOT es> <20071114102159 DOT GA18599 AT calimero DOT vinschen DOT de> <473AD483 DOT C0614E54 AT tid DOT es> <473AF75E DOT 2020707 AT cygwin DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

"Larry Hall (Cygwin)" ha escrito:

> Joaquín Mª López Muñoz wrote:
> > Corinna Vinschen ha escrito:
> >
> >> Use `cvs annotate' to find the date when sa_sigaction has been
> >> introduced and then check against the release dates.  So, from what I
> >> can tell, 1.5.7 should already have sa_sigaction.  sa_sigaction has been
> >> introduced immediately when introducing the file include/cygwin/signal.h
> >> on 2003-11-03, while Cygwin 1.5.7 has been released on 2004-01-31.
> >
> > These dates are correct, but there's no include/cygwin/signal.h in my
> > local copy of cygwin. I don't know which exact Cygwin package would
> > bring that header in.
>
> <http://cygwin.com/cgi-bin2/package-grep.cgi?grep=include%2Fcygwin%2Fsignal%5C.h>

Umm... I think the implied result that cygwin/signal.h *begun* to be supported
in Cygwin 1.5.11 is not correct, as it looks like 1.5.11 is as far in the past as
the package grep tool can go:

http://cygwin.com/cgi-bin2/package-grep.cgi?grep=include%2Fstdio.h


> >> However, why is it important to know?  Just use the latest Cygwin
> >> version and you're done.
> >
> > In order to support legacy environments. I'm doing this reasearch in connection with
> > the Boost Config Library (http://boost.org/libs/config/config.htm ).
>
> Still not clear why it's important for you to live in the past.  What
> exactly about upgrading is the problem?

Boost policy is to try to support as many platforms as possible, within
reasonable limits, rather than forcing users to upgrade to the latest version
of their particular environment. Boost.Config merely codifies the particular
features and quirks of each platform so as to ease the task of writing
cross-platform code; I'm trying to fine tune an aspect of Boost.Config
(a macro called BOOST_HAS_SIGACTION) for the Cygwin familiy.

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -