GNU Libtool 2.2.6 *RE*released

[Gary V. Vaughan]

I'm embarrassed to announce the release of GNU Libtool 2.2.6a.

This release is identical to yesterday's 2.2.6 release, except that
I've calculated the libltdl version number correctly.  I was
overzealous about the library interface changes, and released 2.2.6
to build libltdl.so.9 as it's soname (making it incompatible with
earlier releases from the 2.2 branch using libltdl.so.7).

My theory was that we had removed some of the argz access points
that were accidentally exported on non-GNU/Linux machines, that
strictly would require a new soname.  Since 2.2 is a maintenance
branch, and since the removed access points were not documented
and should not have been visible in any case, I've pulled the
2.2.6 release and tarballs from ftp.gnu.org, and replaced them
with equivalent files named with `2.2.6a'.  The mirrors should
catch up shortly.

When built and installed, the 2.2.6a libtool releases will still
be called 2.2.6 in the install tree, and are identical to yesterdays
release in every way, with the exception of using the correct
soname for libltdl, so that backwards compatibility with earlier
stable 2.2 releases is not broken.  To avoid confusion with the
broken 2.2.6 tarballs, I've simple changed the new filenames to
use 2.2.6a.

A working libtool-2.2.6 is available now from ftp.gnu.org, along
with diffs and against libtool-2.2.4.  Please use a mirror to
reduce stress on the main gnu machine:

 http://www.gnu.org/order/ftp.html

Here are the compressed sources:

 ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a.tar.gz
 ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a.tar.lzma

Here are the diffs against libtool-2.2.4:

 ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4-2.2.6a.diff.gz

Here are the gpg detached signatures:

 ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a.tar.gz.sig
 ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a.tar.lzma.sig
 ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4-2.2.6a.diff.gz.sig

You should download the signature named after any tarball you download,
and then verify its integrity with, for example:

 gpg --verify libtool-2.2.6a.tar.lzma.sig

Here are the MD5 and SHA1 checksums (note these are different to
yesterdays broken release):

 8ca1ea241cd27ff9832e045fe9afe4fd         libtool-2.2.6a.tar.gz
 b121e4848cc53fdd69e796aed73b9ccf         libtool-2.2.6a.tar.lzma
 edbb99827bbfaa687f67cb75b77dff05         libtool-2.2.4-2.2.6a.diff.gz
 7b547877b1b78b547343e4678a531aece8949904 libtool-2.2.6a.tar.gz
 7c5fdce11777261a6c407fe97ac8a1ae5fe99d2b libtool-2.2.6a.tar.lzma
 8fb591cc2e995b1ce14d95206e33df3cf611639e libtool-2.2.4-2.2.6a.diff.gz

This release was bootstrapped with autconf-2.62 and automake-1.10.1,
but is useable with any reasonably modern equivalents in your own
projects.

Alternatively, you can fetch the unbootstrapped source code with
git by using the following command:

 $ git clone git://git.savannah.gnu.org/libtool.git
 $ cd libtool
 $ git checkout v2.2.6a

You will then need to have the latest release versions of Automake
(1.10.1) and Autoconf (2.62) installed to bootstrap the checked out
sources yourself.

Please report bugs to <address@hidden>, along with the verbose
output of any failed test groups, and the output from `./libtool -- 
config.'
The README file explains how to capture the verbose test output.

Apologetically,
        Gary
--
Email me:          address@hidden                          ._(()
Read my blog:      http://blog.azazil.net                 \' )
And my other blog: http://www.machaxor.net                =( \
...and my book:    http://sources.redhat.com/autobook     _(~_)'