Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
Date:	Wed, 7 Nov 2001 17:57:22 +0100
From:	Corinna Vinschen <cygwin-apps AT cygwin DOT com>
To:	cygapp <cygwin-apps AT cygwin DOT com>
Subject:	Re: Did I find an error in the current binutils or what???
Message-ID:	<20011107175722.A2965@cygbert.vinschen.de>
Mail-Followup-To:	cygapp <cygwin-apps AT cygwin DOT com>
References:	<20011107131736 DOT U2965 AT cygbert DOT vinschen DOT de> <3BE94852 DOT 8080303 AT ece DOT gatech DOT edu> <20011107163919 DOT Y2965 AT cygbert DOT vinschen DOT de> <3BE95990 DOT 2000308 AT ece DOT gatech DOT edu>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<3BE95990.2000308@ece.gatech.edu>; from cwilson@ece.gatech.edu on Wed, Nov 07, 2001 at 10:56:00AM -0500

On Wed, Nov 07, 2001 at 10:56:00AM -0500, Charles Wilson wrote:
> Corinna Vinschen wrote:
> 
> 
> >>Except that the cygwin1.dll/libcygwin.a that you are linking against does 
> >>not have the requisite auto-import support thunks (_nm__*).  Perhaps this 
> >>cygwin was compiled using a (very) old binutils?  pre-20010802 ?
> >>
> > 
> > Yes.  It has been cross-compiled on a Linux box.  The binutils are...
> > uhm... compiled on 2001-07-12 so they are definitely pre-20010802.
> > Somehow I don't understand how that stuff is supposed to work.  I'm
> > not a binutils expert...
> 
> 
> Okay, then I'm gonna assume that you are linking against a kernel that you 
> built yourself, and not the "official" cygwin kernel that cgf built 
> (otherwise, the following applies to him):
> 
> You ought rebuild your cross-binutils from the binutils-20011002-1-src as 
> distributed from the cygwin mirrors.
> 
> Recent binutils (post-20010802) add special autoimport-support thunks to 
> the dll's that they create.  These are used to create a lookup table for 
> the variable exports, by fooling the windows runtime loader.  (I don't 
> understand the whole thing, but it's a neat concept.)
> 
> Anyway, the *DLL* as well as your client app need to be built using a 
> recent binutils, in order for the auto-import thing to work properly.

Thanks, that helped.  I have build and installed binutils-20011002-1
for cross-building cygwin binaries on my Linux box.  Now the message

Warning: resolving ___progname by linking to __imp____progname (auto-import)

is written to stderr and the link stage is successfully completed.

> Of course, with the cygwin1.dll, auto-import shouldn't be necessary. 
> __progname *ought* to be declared (with appropriate __declspec() markings) 
> in some header file somewhere, so that's a cygwin bug.

Which is kinda mess since there's even no header on Linux which
defines __progname.  Is there _any_ standard on where to define
__progname?

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

- Raw text -