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 Subject: Re: Invalid compiler error From: Robert Collins To: Tron Thomas Cc: Max Bowsher , cygwin@cygwin.com In-Reply-To: <3E7A2C34.7060302@verizon.net> References: <3E7A0A1F.3010007@verizon.net> <022101c2ef1e$83814660$dd5c893e@pomello> <3E7A2648.7070802@verizon.net> <029101c2ef21$c3788550$dd5c893e@pomello> <3E7A2C34.7060302@verizon.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-QpJEWdcXSrWuV/q08Fbg" Organization: Message-Id: <1048194278.22179.12.camel@localhost> Mime-Version: 1.0 Date: 21 Mar 2003 08:04:38 +1100 --=-QpJEWdcXSrWuV/q08Fbg Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2003-03-21 at 08:01, Tron Thomas wrote: > I'm sorry. I misread what you wrote. I thought you were suggesting=20 > that I try the #elif directive in simple coding example to see if the=20 > compiler would accept it. This is was I used: > This program compiles just fine, and if I define the proper value, it=20 > print the expected text. So it looks like the #elif directive, in=20 > general, is compatable with the Cygwin compiler. It doesn't explain why=20 > the error message still occurs. I suppose I could try changing the code=20 > to what you actually suggested and see if that works. IIRC the elif directive requires the define to be, well, defined. the error you got suggests to me that #elif defined(_WIN32)=20 would be a better test. Rob --=20 GPG key available at: . --=-QpJEWdcXSrWuV/q08Fbg Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+eizmI5+kQ8LJcoIRAp8cAKCsr71JsyXN+TRn0bdCihHfH5mCFgCeJk6D BGC4z5bFiNuzEHtoSdP3Ibw= =j9JZ -----END PGP SIGNATURE----- --=-QpJEWdcXSrWuV/q08Fbg--