public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stephen Davies <scldad@sdc.com.au>
To: cygwin@sourceware.cygnus.com
Subject: Broken C code
Date: Thu, 27 Jan 2000 18:54:00 -0000	[thread overview]
Message-ID: <200001280253.NAA06143@mustang.sdc.com.au> (raw)

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@sdc.com.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@sourceware.cygnus.com

             reply	other threads:[~2000-01-27 18:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-27 18:54 Stephen Davies [this message]
2000-01-27 19:15 ` Chris Faylor
2000-01-27 21:22   ` Stephen Davies
2000-01-27 22:19   ` Stephen Davies
2000-01-28 13:58     ` Chris Faylor
2000-01-29 11:44     ` Mumit Khan
2000-01-27 20:20 ` Terry Lincoln
2000-01-29 11:34 ` Mumit Khan
2000-01-27 22:58 Earnie Boyd
2000-01-27 23:37 ` Stephen Davies
2000-01-28  5:40 N8TM

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200001280253.NAA06143@mustang.sdc.com.au \
    --to=scldad@sdc.com.au \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).