Message-ID: <49C2556A.1070701@gmail.com>
Date: Thu, 19 Mar 2009 14:23:38 +0000
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Message during linking
References: <gpthdl$7o4$1@ger.gmane.org> <49C24FD4.2090908@gmail.com> <gptj64$eon$1@ger.gmane.org>
In-Reply-To: <gptj64$eon$1@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Eric Lilja wrote:
> Dave Korn wrote:
>> It has started to happen now because libstdc++ is a DLL for the first
>> time. We've fixed upstream ld to enable the feature by default and these 
>> warnings will disappear in the next binutils release.

  Hmm, it occurs to me that for the benefit of users with older binutils I
could add -Wl,--enable-auto-init to the compiler's specs for a release or two.

> Ok, sounds great! And the benefits of a libstdc++ as a DLL is reduced
> code size?

  Yep, plus exceptions being throwable from DLLS.

>>   Add -Wl,--enable-auto-import to those LDFLAGS.
> 
> Is that preferred over -enable-auto-import ? 

  I was surprised the unadorned version even worked.  Yes, since you are
(correctly) using the compiler driver to invoke the linker, you should use the
-Wl prefix that means "pass this through to the linker".

> Also, will the next test release be 4.3.3 or 4.3.2?

  4.3.3.

> Also, thanks for your detailed reply Dave and thanks alot for your work
> on gcc! It's fun to use cygwin again with 1.7 and a shiny new gcc!

  Still got a bit of polishing to do on the compiler :)

    cheers,
      DaveK


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