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: <02a901c34b08$2c0c21c0$fd19fea9@caesar> From: "Attila Szegedi" To: References: Subject: Re: #define _POSIX_REALTIME_SIGNALS causes parse error in sys/signal.h Date: Tue, 15 Jul 2003 21:34:55 +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: 753883d0182cc9b386846cdbec35ac3d ----- Original Message ----- From: "Igor Pechtchanski" To: "Attila Szegedi" Cc: Sent: Tuesday, July 15, 2003 8:30 PM Subject: Re: #define _POSIX_REALTIME_SIGNALS causes parse error in sys/signal.h > > Try staring long and hard at the output of "gcc -E sample.c"... ;-) Okay. After preprocessing these lines read (modulo e-mail introduced line breaks): int __attribute__((__cdecl__)) sigwaitinfo (const sigset_t *set, siginfo_t *info); int __attribute__((__cdecl__)) sigtimedwait (const sigset_t *set, siginfo_t *info, const struct timespec *timeout); I still see nothing suspicious near "siginfo_t"... These lines still look like legal C declarations. 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/