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: <20020520212232.36691.qmail@web14505.mail.yahoo.com> Date: Tue, 21 May 2002 07:22:32 +1000 (EST) From: =?iso-8859-1?q?Danny=20Smith?= Subject: RE: binutils status? To: cygwin-apps AT cygwin DOT com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit --- Robert Collins wrote: > > > > -----Original Message----- > > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > > Sent: Tuesday, May 21, 2002 1:07 AM > > > Since --auto-import has been the default for the last version > > of binutils, I think we should leave it that way. > > Yes. > > > I think we should keep the warnings if --auto-import isn't > > specified on the command line but get rid of them if it is > > explictly specified. Including --auto-import on the command > > line would indicate that the user knows what they're doing, > > so they don't need to see warnings. > > Works for me. > Agree This addresses my main concern of no warnings and is similar to the way --enable-stdcall-fixup works now. Danny > Rob http://briefcase.yahoo.com.au - Yahoo! Briefcase - Save your important files online for easy access!