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: <02ce01c34b19$ce391960$fd19fea9@caesar> From: "Attila Szegedi" To: Subject: How to get sigwait()? Date: Tue, 15 Jul 2003 23:41:09 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4925.2800 X-Authenticated-Sender: 3353acbbe371c82e167c409400781305 This is kind of follow-up to my question about _POSIX_REALTIME_SIGNALS: what is (is there?) the proper way to get compiled some code under Cygwin (originally written for Linux) that uses the sigwait() function? I first naively thought that defining _POSIX_REALTIME_SIGNALS is enough to conditionally compile relevant parts in /usr/include/sys/signal/h. Then it turned out that if I define _POSIX_REALTIME_SIGNALS, I must also define __rtems__ to trigger conditional compilation of the siginfo_t struct. Now, this rings the alarm bells in my head. Am I really supposed to define a symbol indicating that the compilation target is an embedded RTOS when I want to have the code compiled for Windows? If not, what is the solution? Is there any? Thanks in advance for any responses Cheers, Attila. -- 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/