On Tue, 10 Oct 2017, Nick Clifton wrote:
> > I do not know
> > if there are other local libtool changes that are not in version 2.4.6; it
> > would be necessary to check all differences from 2.2.7a to determine
> > whether any need to be re-applied to 2.4.6.
>
> *sigh* It seems that 2.2.7a was not an official release. At least I could
> not find a tarball for that specific version on the ftp.gnu.org/libtool
> archive.
> (There is a 2.2.6b release and a 2.2.8 release but no 2.2.7<anything>). So it
> looks like we have been using a modified set of sources for a long time now.
Well, it looks like the update from upstream was
r155012 | rwild | 2009-12-05 17:18:53 +0000 (Sat, 05 Dec 2009) | 113 lines
Sync from git Libtool and regenerate.
so looking for relevant libtool commits around that time might help
identify the one that was used. My guess is that
commit ef32f487d746dbcdc00c2c357ebe3cf2a68d8a28
Author: Ralf Wildenhues <ralf.wildenh...@gmx.de>
Date: Tue Nov 24 12:22:13 2009 +0100
Enable symbol versioning with the GNU gold linker.
is the libtool commit you should be comparing libtool files with to
identify local changes.
--
Joseph S. Myers
jos...@codesourcery.com
