X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49C2556A.1070701@gmail.com> Date: Thu, 19 Mar 2009 14:23:38 +0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Message during linking References: <49C24FD4 DOT 2090908 AT gmail DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 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/