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 Message-ID: <02e801c34b1c$7e556900$fd19fea9@caesar> From: "Attila Szegedi" To: References: Subject: Re: #define _POSIX_REALTIME_SIGNALS causes parse error in sys/signal.h Date: Wed, 16 Jul 2003 00:00:24 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4925.2800 X-Authenticated-Sender: b3432d222fa812a3f8abd6e54a7ce91f ----- Original Message ----- From: "Igor Pechtchanski" To: "Attila Szegedi" Cc: Sent: Tuesday, July 15, 2003 11:52 PM Subject: Re: #define _POSIX_REALTIME_SIGNALS causes parse error in sys/signal.h > > What about the declaration of "siginfo_t" ~100 lines earlier? Yup, that's it - I started a separate thread to ask this one. It's there, but guarded with #if defined(__rtem__) I just don't feel it's safe to define __rtem__ when attempting to compile for Windows... You see, those headers are generic Cygnus headers, so they contain code for Cygnus embedded targets as well. For some reason, siginfo_t is compiled only when __rtem__ is defined... Anyway, that piece of code (essentially a signal handler) isn't *that* much critical - signals are used only to implement few auxiliary services - so maybe I'll just end up omitting it altogether. I understand that UNIX signals might not be properly emulated under Windows. pthread_yield would be critical to have, though. 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/