Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <4372B18D.6020003@pacom.com> Date: Thu, 10 Nov 2005 13:33:49 +1100 From: Scott Finneran User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Problem: sigrelse() in winsup but not defined in signal.h References: <43729FAA DOT 1050706 AT pacom DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailGuard-ID: 4372b1251769fe X-Filtered: by MailGuard - visit http://www.mailguard.com.au X-IsSubscribed: yes 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. Cheers, Scott Igor Pechtchanski wrote: > On Thu, 10 Nov 2005, Scott Finneran wrote: > > >>I am trying to compile something under cygwin but am hitting a snag with >>sigrelse(). I am running the latest binary downloaded by setup.exe. > > > Please see for instructions on reporting > your Cygwin version properly. However... > > >>It appears to be defined in winsup/cygwin/exceptions.cc (in CVS) but is not >>declared in signal.h so of course the compile fails. >> >>Is there any reason for this? > > > There were some changes in CVS since the last official Cygwin release. > Try installing a full snapshot from (make > sure to get the -inst tarball, which includes the headers). > HTH, > Igor -- Message protected by MailGuard: e-mail anti-virus, anti-spam and content filtering. http://www.mailguard.com.au/mg -- 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/