Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Subject: RE: libtool devel package still dll crippled. Date: Sun, 14 Apr 2002 20:52:58 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message From: "Robert Collins" To: "Ralf Habacker" , "Cygwin-Apps" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3EAspL07374 > -----Original Message----- > From: Ralf Habacker [mailto:Ralf DOT Habacker AT freenet DOT de] > Sent: Sunday, April 14, 2002 6:15 PM > I had recgonized problems with the > allow_undefined_flag=unsupported and have tried only with > "no", which works. Yet I have tried with "yes" it works too. > So its no problem for me to use "yes". Cool. Using yes (or blank, blank is preferred IIRC), means that a purely unix package will build .dll's on cygwin, without any hacks needed (given the auto-import caveats_. > _LT_AC_TAGVAR(always_export_symbols, $1)=yes > > Using "yes" causes libtool to use nm to generate a symbol > list, which is avoided by setting to "no". Are the symbol tables identical in both cases? Would Danny's whole archive patch help the symbols? I think there must be some way to prevent ld outputting the imported symbols as well as the exported symbols... Anyway, setting always_export to 'no' should be ok for now. Over the next week I'll do some testing and get back to the list. Rob