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: <20020903185351.39938.qmail@web21009.mail.yahoo.com> Date: Tue, 3 Sep 2002 11:53:51 -0700 (PDT) From: Nicholas Wourms Subject: [g++-3.2]: libstdc++.a does not contain relocatable objects To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Ok, Chris I know you don't have the cycles for this, so I prefacing it by saying I'm trying my best to look into it. Now that we have that behind, here's what I've discovered so far in why libtool won't link properly when building c++ libraries with g++-3.2. I did a "objdump -f /usr/lib/libstdc++.a" and discovered that none of the object files had the relocatable flag set (which is what libtool looks for in shared library archives). To confirm my suspicion, I did the same procedure on g++-2's libstdc++.a. This time, though, the relocatable flag was set on the object files contained within. Furthermore, the g++-3.2 libstdc++.a archive for mingw also contains relocatable objects. So the question is: What has changed in the configuration scripts between gcc 2.95 and 3.2 which causes this to build static for cygwin? Well for starters, I have more than a suspicion that the gcc people, in their attempt to upgrade to newer autotools, have mucked up the support for Cygwin shared libraries. I'm currently investigating this, but some assistance would be appreciated. Note that I'm running the latest cygwin dll built from cvs sources on a Windows ME machine. Also note that this behavior has been apparent since the gcc-3.1.1 release (and possibly before that). Cheers, Nicholas __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/