Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 19 Sep 2003 17:34:09 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: getopt: ugly linker messages
Message-ID: <20030919153409.GF9981@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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> <3F6B0965 DOT 3050304 AT cwilson DOT fastmail DOT fm> <20030919151803 DOT GE17232 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030919151803.GE17232@redhat.com>
User-Agent: Mutt/1.4.1i

On Fri, Sep 19, 2003 at 11:18:03AM -0400, Christopher Faylor wrote:
> On Fri, Sep 19, 2003 at 09:49:25AM -0400, Charles Wilson wrote:
> >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.)
> 
> I'm willing to do this but I have the same reservations that I think
> you're expressing above, Chuck.  Also, the auto-import of data variables
> is slower than a normal dllimport so I don't feel real comfortable about
> making this the default.
> 
> I don't feel really strongly about this however, so if the consensus is
> that this should be turned on, I'll make a cygwin-specific change to
> binutils.

No need.  It's just a bit annoying.

However, isn't that an error in binutils?  If I have

  extern int __declspec(dllimport) foo;

and 100 lines later I have a

  extern int foo;

why is then the information about the __declspec removed?  Shouldn't
that information be kept?  AFAIK, the "extern" storage class shouldn't
change any information already known about the variable in question.
It should complain about e.g. conflicting types but it should never
change what's already there.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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/