Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3BCB033A.6020106@ece.gatech.edu> Date: Mon, 15 Oct 2001 11:39:38 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Roger Wells CC: cygwin AT cygwin DOT com Subject: Re: global data in DLL's References: <00ea01c15575$a91d7860$f05a798b AT mtg DOT saic DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Umm...so you've been explicitly #defining stuff as *_imp__stuff all this time? That's NOT the right way to do it. You should be using declspec(dllimport) stuff instead -- which will do the right thing, automatically. See dllhelpers-0.2.6 here: http://www.neuro.gatech.edu/users/cwilson/cygutils/V1.1/dll-stuff/ (BTW, the very latest binutils allows you to dispense with all that _imp__stuff completely -- but it only works with gcc/binutils. See dllhelpers-0.2.9 for more info. --Chuck Roger Wells 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 > > Roger Wells, P.E. > SAIC > 221 Third St > Newport, RI 02840 > 401-847-4210 (voice) > 401-849-1585 (fax) > roger AT mtg DOT saic DOT com > > > > -- > 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/ > > -- 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/