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: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: libtool devel auto-import broken MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Sun, 17 Mar 2002 21:18:35 +1100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: libtool devel auto-import broken Thread-Index: AcHNnE4JIuXNmH+NQIiUyf21nDftIAAALQ4Q From: "Robert Collins" To: "Stephano Mariani" , "Charles Wilson" Cc: "CygWin-Apps" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g2HAIgW27177 > -----Original Message----- > From: Stephano Mariani [mailto:sk DOT mail AT btinternet DOT com] > Sent: Sunday, March 17, 2002 9:12 PM > To: 'Charles Wilson'; Robert Collins > Cc: 'CygWin-Apps' > Subject: RE: libtool devel auto-import broken > > > I would like to test these new versions of the autotools if I > may. I am a very autotools dependent user and use it > frequently enough to warrant dissecting it and learning much > more about their internals :) > > I have noticed however that using automake (1.5) and libtool > (1.4e) there is no way to prevent symbols being exported. I > have therefore had to resort to patching my binutils to > prevent every symbol from being exported :( There is a bin-utils export-filter command you can use instead of patching IIRC. Mind you, we resorted to patching binutils to get libtool to do what we want :]. Rob