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: Sat, 21 May 2005 13:36:00 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Splint parseerror with Message-ID: <20050521113600.GM2794@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On May 20 23:37, only4 wrote: > # 19 may 2005: > !!!!CATCHED!!!! > I re-read the directive > #if defined(_POSIX_THREADS) && !defined(__CYGWIN__) > and realized that splint may have not __CYGWIN__ setted... > > splint +D__CYGWIN__ file.c > > WORKS! > This can suggest further investigation, to find > why the missing __CYGWIN__ ? > are there other missing flags too? > > # 20-may-2005: > I'm now investigatin who sets __CYGWIN__, and why splint don't have it. See /lib/gcc-lib/i686-pc-cygwin/3.3.3/specs. It's set by gcc itself for cpp. splint could set it by default, that would be pretty straightforward. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.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/