Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3F6B0965.3050304@cwilson.fastmail.fm> Date: Fri, 19 Sep 2003 09:49:25 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: getopt: ugly linker messages References: <200309181953 DOT h8IJrMWa017255 AT bolt DOT sonic DOT net> <20030918195607 DOT GA11311 AT redhat DOT com> <3F6A7C70 DOT 7030901 AT cwilson DOT fastmail DOT fm> <20030919064843 DOT GM9981 AT cygbert DOT vinschen DOT de> In-Reply-To: <20030919064843.GM9981@cygbert.vinschen.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Corinna Vinschen wrote: > Since that auto-import is working fine for a long while now and since > this sort of auto-import is normal for any other platform... isn't there > a time we can get rid of that message? auto-import is not the default for all pei386 versions of binutils, particularly mingw. And auto-import is in no way "normal". It provides functionality that, on the surface, appears to emulate the normal behavior of other platforms -- but under the hood, it's a bizzarre beast. So, taking those two points into consideration, I'm not sure what the right thing to do is, without ticking somebody on some platform off. The current compromise seems to be mostly acceptable. Perhaps a cygwin-special (e.g. doesn't go back to binutils CVS) patch? In that case, it's a one-liner -- just change the default value of link_info.pei386_auto_import to '1' instead of '-1' in pe.em (you might also need to change the default in ldmain.c, but I don't think that's necessary.) -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/