Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
From: Chris Faylor <cgf@cygnus.com>
Date: Tue, 4 Jul 2000 23:30:56 -0400
To: cygwin@sourceware.cygnus.com
Subject: Re: binutils-20000625 and --enable-auto-image-base
Message-ID: <20000704233056.A3973@cygnus.com>
Reply-To: cygwin@sourceware.cygnus.com
Mail-Followup-To: cygwin@sourceware.cygnus.com
References: <39629555.D74ABFDD@ece.gatech.edu> <200007050153.VAA03219@envy.delorie.com> <3962989F.B1FAB50E@ece.gatech.edu> <20000704220656.A3751@cygnus.com> <3962A0EF.5CF9AAEB@ece.gatech.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <3962A0EF.5CF9AAEB@ece.gatech.edu>; from cwilson@ece.gatech.edu on Tue, Jul 04, 2000 at 10:43:59PM -0400

On Tue, Jul 04, 2000 at 10:43:59PM -0400, Charles Wilson wrote:
>Chris Faylor wrote:
>> 
>> On Tue, Jul 04, 2000 at 10:08:31PM -0400, Charles Wilson wrote:
>> >Well, he seems to have submitted it to the main binutils list
>> >(http://sourceware.cygnus.com/ml/binutils/1999-q3/msg00538.html). But, I
>> >can't seem to find any evidence that it was actually committed in the
>> >main binutils.
>> >
>> >Is it possible to include Mumit's patch, and the one posted by Eric
>> >Fifer a few days ago, and release another version of cygwin-binutils (or
>> >push those two patches into the main binutils, since you're releasing
>> >out of sourceware)? I will try to sync up Mumit's patch with the
>> >20000625 source code tonight...
>> 
>> It's possible.  Maybe DJ will even be able to commit Mumit's change.
>> 
>> I don't know what Eric Fifer's change was but if it is the dllwrap
>> fix, it's already in cvs.
>
>Yes, you are correct. I just checked the cvsweb interface and Eric's
>change had been committed.
>
>The binutils-20000625-src.tar.gz is not *strictly* a pure
>out-of-sourceware release. The cvs shows that only the first part of my
>changes to emultempl/pe.em are there, but all of my changes to that file
>appear in the cygwin-specific tarball. 

That's right.  I added your changes after I noticed that not all had
been applied.

>The workaround, of course, is to fix the dlltool command so that the
>import lib is called 'libperl5_6_0.dll.a'. We can deal with these issues
>in the cygwin community, but I don't think it's a good idea to
>inconvenience the rest of the pei386 folks with these most recent
>changes just yet.

Is there any reason why 'ld' can't import data from the DLL?  Wouldn't
that fix this problem?

cgf

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