This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Support for sa_sigaction


JoaquÃn MÂ LÃpez MuÃoz wrote:
"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


I wasn't attempting to point you to the answer to your question of what
package signal.h comes from as opposed to when it was first introduced.
Corinna's pointers there are better for that.



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.


I understand.  Of course, given that 1.5.7 is more than 3 years old,
some arbitrarily more recent version of Cygwin may make things easier for
you.  On a different note, versions other than the current are not supported
by this list so using very old versions is already discouraged and puts the
user into "you're on your own" land.


-- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746

_____________________________________________________________________

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]