public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Chris Faylor <cgf@cygnus.com>
To: Stephen Davies <scldad@sdc.com.au>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Broken C code
Date: Thu, 27 Jan 2000 19:15:00 -0000	[thread overview]
Message-ID: <20000127221504.A8019@cygnus.com> (raw)
In-Reply-To: <200001280253.NAA06143@mustang.sdc.com.au>

On Fri, Jan 28, 2000 at 01:23:44PM +1030, Stephen Davies wrote:
>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?

It sounds like your specs file is screwed up.  It should be in something
like .../lib/gcc-lib/cygnus-2.7b19/specs but I don't know precisely where
it would be located.

It should contain a line like this:

*predefines:
-Di386 -D_WIN32   -DWINNT  -D_X86_=1 -D__STDC__=1  -D__stdcall=__attribute__((__stdcall__))   -D__cdecl=__attribute__((__cdecl__))   -D__declspec(x)=__attribute__((x))   -Asystem(winnt) -Acpu(i386) -Amachine(i386)

This is from a much more recent gcc compiler so this may not be exactly right
but you can at least see what it should look like.

It's possible that you also may have something like a GCC_LIBRARY environment
variable which is pointing to the wrong place.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-01-27 19:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-27 18:54 Stephen Davies
2000-01-27 19:15 ` Chris Faylor [this message]
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=20000127221504.A8019@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=scldad@sdc.com.au \
    /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).