Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<20011015203220.86755.qmail@web14509.mail.yahoo.com>
Date:	Tue, 16 Oct 2001 06:32:20 +1000 (EST)
From:	=?iso-8859-1?q?Danny=20Smith?= <danny_r_smith_2001 AT yahoo DOT co DOT nz>
Subject:	Re: global data in DLL's
To:	Roger Wells <ROGER DOT K DOT WELLS AT saic DOT com>, cygwin AT cygwin DOT com
In-Reply-To:	<00ea01c15575$a91d7860$f05a798b@mtg.saic.com>
MIME-Version:	1.0

 --- Roger Wells <ROGER DOT K DOT WELLS AT saic DOT com> wrote: > Up until gcc 2.95.2
global data needed to be redefined as:   global ->
> (*__imp_global) or (*_imp__global)
> as of 2.95.3 it seems that only (*_imp__global) works.
> Can this be overridden?  Can it be reversed?  I have lots of build
> scripts
> that depend on the former definition.  These all need to be modified in
> order to migrate the 2.95.3
>

Have you tried the --compat-implib option?

  --compat-implib     Create backward compatible import libs;
                      create __imp_<SYMBOL> as well.


Danny




http://briefcase.yahoo.com.au - Yahoo! Briefcase
- Manage your files online.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -