X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 14 Nov 2007 11:21:59 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Support for sa_sigaction Message-ID: <20071114102159.GA18599@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <473AC8C0 DOT 22E4822B AT tid DOT es> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <473AC8C0.22E4822B@tid.es> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Nov 14 11:06, Joaqu?n M? L?pez Mu?oz wrote: > Hello, > > The latest releases of Cygwin support include sa_sigaction member in the > structure sigaction, but older releases such as Cygwin 1.5.7 don't (I've just > checked it out with my 1.5.7 local copy). > > How can I find the exact Cygwin release where sa_sigaction began to be > supported? I've scanned the web, the mailing lists archive and the CVS repo > looking for this piece of info, to no avail. 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. However, why is it important to know? Just use the latest Cygwin version and you're done. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/