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
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Fri, 28 Jan 2000 16:58:08 -0500
To:	Stephen Davies <scldad AT sdc DOT com DOT au>
Cc:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: Broken C code
Message-ID:	<20000128165808.A10440@cygnus.com>
Mail-Followup-To:	Stephen Davies <scldad AT sdc DOT com DOT au>,
	cygwin AT sourceware DOT cygnus DOT com
References:	<cgf AT cygnus DOT com> <200001280619 DOT QAA06487 AT mustang DOT sdc DOT com DOT au>
Mime-Version:	1.0
X-Mailer:	Mutt 1.0i
In-Reply-To:	<200001280619.QAA06487@mustang.sdc.com.au>; from scldad@sdc.com.au on Fri, Jan 28, 2000 at 04:49:04PM +1030

On Fri, Jan 28, 2000 at 04:49:04PM +1030, Stephen Davies wrote:
>OK. That does solve the problem:-))
>
>My specs file looked OK but did not include the declspec define. Adding it in 
>got me going again.
>
>At least, it gets me to the point where I can compile and run the executable.
>
>It is not the complete answer though. I still get several hundred:
>
>warning: 'dllexport' attribute directive ignored
>
>messages.
>
>Also, it does not explain what happened to break my setup.
>
>Is this declspec definition in specs new?
>
>What is it for?

It may be new.  I don't remember how it used to be done.  Possibly it was just
compiled into gcc.

>Thanks again Chris,

I don't think I really solved your problem.  In fact, I may have just complicated
things with my suggestion.  I just don't remember what that version of the compiler
was like.

If gcc is choking on the __attribute__(dllexport) then my suggestion is probably
wrong.  Sorry.

Have you tried doing a compile with "gcc -v" and verifying that all of the paths
are as you'd expect?

cgf

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

- Raw text -