Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<20000128065817.2986.qmail@web121.yahoomail.com>
Date:	Thu, 27 Jan 2000 22:58:17 -0800 (PST)
From:	Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To:	earnie_boyd AT yahoo DOT com
Subject:	Re: Broken C code
To:	Stephen Davies <scldad AT sdc DOT com DOT au>, cygwin AT sourceware DOT cygnus DOT com
MIME-Version:	1.0

It wouldn't be the \r\n line endings would it?

--- Stephen Davies <scldad AT sdc DOT com DOT au> wrote:
> Hello.
> 
> I have managed to break my ability to compile a number of C programs with gcc
> 
> 2.7B19 under cygwin B19.1.
> 
> In September 1999, all of these programs compiled successfully on the same 
> machine with the same cygwin environment.
> 
> Now, all of the programs involved fail to compile with the same error
> messages 
> and I haven't a clue as to why.
> 
> In all cases, the following code is included from a vendor-specific set of 
> headers:
> 
> typedef  IDI_ULONG  (__attribute__((__stdcall__))  *  OPI_DELETE_CALLBACK ) 
> (OPI_CONID, OPI_FILEID);^M
> __declspec(dllexport)   IDI_USHORT  __attribute__((__stdcall__))  
> OpiMakeConnection( OPI_PCONID pConID );^M
> 
> (This is just two of many similar lines)
> 
> This produces the following compiler message:
> 
> ../include/opiob.h: In function '__declspec':
> In file included from ../include/opi.h:283,
>                        from cic.h:1,
>                        from getpk.c:1
> ../include/opiob.h:141 parse error before '__declspec'
> ../include/opiob.h:140 declaration for parameter 'OpiMakeConnection' but no 
> such parameter
> 
> followed by a whole bundle of similar errors.
> 
> Can anyone please explain to me what I have done/not done to cause this 
> misinterpretation of the __declspec(dllexport) syntax?
> 
> Cheers and thanks,
> Stephen Davies
> 
> 
> -- 
> ========================================================================
> Stephen Davies Consulting	    		      scldad AT sdc DOT com DOT au
> Adelaide, South Australia.     		          Voice: 08-8177 1595
> Computing & Network solutions.	 	      Fax: 08-8177 0133
> 
> 
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> 
> 

=====
Earnie Boyd <mailto:earnie_boyd AT yahoo DOT com>
Cygwin Newbies, please visit
<http://www.freeyellow.com/members5/gw32/index.html>
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -