Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: <3E7A2648.7070802@verizon.net>
Date: Thu, 20 Mar 2003 12:36:24 -0800
From: Tron Thomas <tron DOT thomas AT verizon DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Max Bowsher <maxb AT ukf DOT net>
CC: cygwin AT cygwin DOT com
Subject: Re: Invalid compiler error
References: <3E7A0A1F DOT 3010007 AT verizon DOT net> <022101c2ef1e$83814660$dd5c893e AT pomello>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out002.verizon.net from [4.65.8.163] at Thu, 20 Mar 2003 14:36:24 -0600

Earlier, I tried almost exactly what you suggested before posting my 
question, and it worked fine with the Cygwin compiler.  Would it be 
helpful if I actually provided the headers the library is using?

Max Bowsher wrote:

>Tron Thomas wrote:
>  
>
>>I wrote a simple program to test an open source library I am planning to
>>use in a development project.  I want the project to be supported on
>>different compilers, including the GCC compiler included with Cygwin.  I
>>have been able to successfully build my test application using the
>>Micrsoft and Borland compilers.  When I try to build the program with
>>the Cygwin compiler, I get a compiler error related to a header file I'm
>>including from the library.
>>
>>Here is the error message I get:
>>
>>#if with no expression
>>
>>This is the line of code that is apparently causing the problem:
>>
>>#elif _WIN32
>>
>>I don't see why this should be causing a problem especially when the
>>other compilers build without any problems.  I use -DWIN32 in the
>>command line arguments I used when I build the application.
>>    
>>
>
>Hmm. Is #elif a valid directive for gcc? I don't know. You could always
>rewrite like:
>
>#if FOO
>
>#else
>#if BAR
>
>#endif
>#endif
>
>Max.
>
>
>  
>



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/