Mail Archives: cygwin-apps/2002/03/17/12:12:30
I made some minor modifications because I am using a patched binutils
(for preventing all symbols in the global scope from being exported)
with which libtool cannot find a sed pattern for finding symbols to
export when a .sym file is not given. The test for the "checking to see
how to parse nm-B output" (or something like that) fails and an empty
sed pattern is tried when searching for symbols causing the build to
Thanks for the URL,
> -----Original Message-----
> From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT edu]
> Sent: Sunday, 17 March 2002 5:6 PM
> To: Stephano Mariani
> Cc: 'Robert Collins'; 'CygWin-Apps'
> Subject: Re: libtool devel auto-import broken
> Okay, the testing versions of automake-devel (automake-1.6) and
> libtool-devel (libtool-20020316) are up at
> If you use the latest setup.exe snapshot, add that URL to the
> locations' list, and use setup to install these test versions.
> P.S. libtool-20020316 passes all of the tests (except quote which
> and build-relink/build-relink2 which are skipped). This is the same
> Stephano -- what minor modifications? My 20020316 version of libtool
> includes Robert's original patch...
> Stephano Mariani wrote:
> > I see. In any case, your patch was just the ticket (with some minor
> > modifications) :). I can now build my libraries as intended without
> > the symbols in the global scope being exported. :)
> > Thanks,
> > Stephano Mariani
> >>-----Original Message-----
> >>From: Robert Collins [mailto:robert DOT collins AT itdomain DOT com DOT au]
> >>Sent: Sunday, 17 March 2002 12:2 PM
> >>To: Stephano Mariani; Charles Wilson
> >>Cc: CygWin-Apps
> >>Subject: RE: libtool devel auto-import broken
> >>>-----Original Message-----
> >>>From: Stephano Mariani [mailto:sk DOT mail AT btinternet DOT com]
> >>>Sent: Sunday, March 17, 2002 10:52 PM
> >>>To: Robert Collins; 'Charles Wilson'
> >>>Cc: 'CygWin-Apps'
> >>>Subject: RE: libtool devel auto-import broken
> >>>I understand that, but you mentioned that what is being
> >>>accomplished by patching binutils is also possible by other
> >>>means that do not involve rebuilding ld; libtool should be
> >>>able to detect this and use the alternate method... I don't
> >>>mind supplying a list of symbols to export.
> >>>If this is not possible, then please excuse my ignorance as
> >>>to the inner workings of libtool :)
> >>Sorry, crossed wires. We needed *different* functionality to what
> >>are talking about, that was what we patched binutils for.
- Raw text -