Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 10 Nov 2005 10:13:53 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Problem: sigrelse() in winsup but not defined in signal.h Message-ID: <20051110091353.GA4770@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <43729FAA.1050706@pacom.com> <4372B18D.6020003@pacom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4372B18D.6020003@pacom.com> User-Agent: Mutt/1.4.2i On Nov 10 13:33, Scott Finneran wrote: > Hello Igor, > > Thankyou for your reply. Firstly, yes I should have done a bit more > reading before posting. I did as you suggested and downloaded the latest > snapshot (winsup-src-20051108). > > The problem that I experienced before still exists in the latest > snapshot. sigrelse() is defined in winsup/cygwin/exceptions.cc but is > not declared in signal.h (sighold() etc. are all declared here). > > Producing a patch to fix this issue is a trivial task which I am more > than happy to do. However, as this situation (defined but not declared) > is such a show-stopper and cygwin always seems to be well tested I > assumed that it was not a bug but some kind of a feature. > > In other words, is the function implemented but not defined > intentionally to prevent people from using it for some unspecified reason? > > Any insight would be appreciated. See my reply to cygwin-patches. It was just a missing prototype. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- 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/