ld --auto-import for cygwin and libtool

Christopher Faylor cgf@redhat.com
Sun Jul 22 20:09:00 GMT 2001

On Mon, Jul 23, 2001 at 12:47:31PM +1000, Travis Howell wrote:
>----- Original Message -----
>From: "Christopher Faylor" <cgf@redhat.com>
>> On Mon, Jul 23, 2001 at 11:19:48AM +1000, Travis Howell wrote:
>> >I tried using that older binutils 20000722-1  again along with
>> >the rest of Cygwin and it still works fine with data exports!
>> >Are you sure you aren't getting the binutils versions confused ? the
>> >announcement (
>> > http://sources.redhat.com/ml/cygwin-announce/2000/msg00041.html ) for
>> >20000722-1 mentions nothing much changed but the announcement (
>> > http://sources.redhat.com/ml/cygwin-announce/2000/msg00091.html ) for
>> >20001029 mentions several changes from dj, cgf and you.
>> I just checked all of my email.  To the best of my knowledge I have
>> never applied a patch from Paul Sokolovsky to binutils.  I could be
>> wrong but I don't see any mail from him to me about this or from me to
>> him.
>> It's possible that something was broken in binutils by subsequent
>> changes.
>> These days, my binutils releases are fairly standard except for a couple
>> of my own cygwin-specific changes which were not accepted by the
>> binutils maintainers.
>A patch from Paul Sokolovsky was in binutils-20001029-2.tar.gz
>Check out http://sources.redhat.com/ml/cygwin-announce/2000/msg00091.html
>and http://www.cygwin.com/ml/cygwin/2000-11/msg00982.html
>Quotes from those messages to save you looking:
>- Fix from Paul Sokolovsky that deals with exporting data
>  variables correctly in conjunction with an --export-all-symbols.
>2000-10-04  Paul Sokolovsky  <Paul.Sokolovsky@technologist.com>
>        * pe-dll.c (make_one): Do not generate code thunk for DATA
>        exports. (process_def_file): deduce DATA flag for
>        auto-export sumbols.

Ok, this game is getting rather tiring.

*I* did not install the patch.  As I said "These days, my binutils
releases are fairly standard".  That means that I just grab the
latest version of binutils from CVS, build it, do some rudimentary
testing, and release it.  I do monitor the binutils mailing list
and, when I see a cygwin-specific change I try to make sure that it
is mentioned when I make the release.  That's what I did in this case.

Paul is a smart person and has contributed patches to binutils.  They
are probably normally added by the binutils PE maintainer -- DJ Delorie
(dj@redhat.com).  They are not added by me.

I hope that Paul's auto-import and other patches make it into the
binutils distribution.  I don't have any power over that project.
Perhaps you should lobby them.

In any event, most of this discussion is pointless.  Even if you found
out that I had dinner with Paul on June 28 at 6:30PM, we both
smoked cigars afterwards, and decided to include all of his patches
in the next release of binutils, the patches are not there now.  So,
let's move on.

It's possible that I might be convinced to include Paul's patches in the
next binutils release if they are not incorporated into the official
release.  However, I would rather use the official CVS release, if


More information about the Cygwin-apps mailing list