Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3CE880A6.6030404@ece.gatech.edu> Date: Mon, 20 May 2002 00:50:46 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin-apps AT cygwin DOT com Subject: Re: binutils status? References: <20020520034224 DOT GA16597 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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