X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_62,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A7ED694.6080108@cwilson.fastmail.fm> Date: Sun, 09 Aug 2009 10:00:52 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: libtool: -{shared,static}-libgcc References: <4A7E7628 DOT 10105 AT users DOT sourceforge DOT net> <4A7ED4AA DOT 60009 AT cwilson DOT fastmail DOT fm> In-Reply-To: <4A7ED4AA.60009@cwilson.fastmail.fm> 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 Charles Wilson wrote: > Yaakov (Cygwin/X) wrote: >> The attached patch (against the latest 2.2.7a snapshot, not taking the >> other patch into account) should allow libtool to accept the >> -{shared,static}-libgcc flags and just pass them on to gcc. > > It just can't be that simple, can it? Well, for *libgcc* I guess it can, > because there is no libgcc.la. Oh, I just thought of something. The user would need to ensure that when libtool is generated (e.g. during configure), LDFLAGS includes the intended -{shared,static}-libgcc flag. Otherwise, libtool's *_postdeps variable will not include the "correct" list of libraries. But then, what happens if you use a different -{static,shared}-libgcc at actual linktime? Or if you link some targets one way, and other targets the other way? -- Chuck -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple