This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: binutils status?
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 20 May 2002 00:50:46 -0400
- Subject: Re: binutils status?
- References: <20020520034224.GA16597@redhat.com>
Christopher Faylor wrote:
> I lost track. Should I make a new release or are we waiting for
> something new to be added?
>
> I just rebuilt binutils and made --auto-import the default. Is there
> a compelling reason for not doing this in the next release? I know that
> --auto-import isn't perfect but will it solve more problems than it
> creates?
Waitaminute. I thought it already was the default. Hmmm...let me go
check...weird, I don't see --enable-auto-import in any of my makefiles,
yet I know that I'm linking to _nm_ symbols...
Hmm...have I been using a local build of ld.exe all this time? Nope,
datestamp on the file is 20011002...
Color me confused.
But if it ain't the default, it should be. And we should probably
remove the warning message that gets printed (around line 908 in pe.em),
or downgrade it so that it only gets printed when -v (verbose).
Other than that, I know of three different things we're still waiting on
(or maybe they've been committed and I missed it):
1) Ralf's "removing unused _nm_ symbol exports" fix
2) Danny's (or Ralf's?) export-list fix (where whole static archives can
be marked for non-export, or DO export...helpful for convenience libs)
3) Ralf's patch for "objdump/cygwin crashes on auto-imported libs"
--Chuck