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 Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3C5E3878.1080909@ece.gatech.edu> Date: Mon, 04 Feb 2002 02:30:00 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: libtool-devel-20020202-1 References: <200202040718 DOT g147IRC03659 AT cgf DOT cipe DOT redhat DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Note: In libtool CVS, a decision was made to rescind the previous "-no-undefined" default. (Reason: if a libraries objects DID have an undefined symbol, then not even a static lib would be built, on cygwin.) This is all related to the MLB restructuring, I think. Anyway, this means that you need to add '-no-undefined' to your libfoo_la_LDFLAGS line in Makefile.am, or be sure to call libtool yourself using the -no-undefined flag. P.S. Ralf -- give this version a shot, and see if it fixes your problems with C++ DLLs. --Chuck Charles Wilson wrote: > The 'libtool-devel' package has been updated to 20020202-1. > It contains a hacked version of libtool(from CVS 02-Feb-2002), > installed into /usr/autotool/devel/*. Basically, this is a > forward port of the hacks from the previous, 20010531 release > to current libtool CVS HEAD. > > The good news: this version passes the "dry-run" test that > the previous one failed. It adds no new selftest failures -- > AND it passes the new C++ libtool testsuite. So, it should > help to solve the problems the 20010531 version had with C++ > code. (I've used to it build the C++ 'libplotter' library from > GNU plotutils.) -- 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/