GNU Libtool 2.2.4 released.

The Libtool Team is pleased to announce the release of GNU Libtool  
2.2.4.

GNU Libtool hides the complexity of using shared libraries behind a  
consistent, portable interface. GNU Libtool ships with GNU libltdl,  
which hides the complexity of loading dynamic runtime libraries  
(modules) behind a consistent, portable interface.

This is a maintenance release from the Libtool 2.2 branch.

Compared to last month's Libtool 2.2.2 release, the new 2.2.4 has  
fixed a number of small bugs, and improved the reliability and  
usability of libtoolize.  Please see the NEWS file in the distribution  
for a comprehensive list of user visible changes.

Despite a new and improved M4 interface to Libtool from Autoconf,  
every effort has been made to retain backwards compatibility with the  
1.5.x interfaces.  Autoupdate (which ships with Autoconf) will help  
you upgrade your configure.ac to the new interface when you are ready  
to migrate.

GNU Libtool 2.2.4 is available now from ftp.gnu.org.  Please use a  
mirror to reduce stress on the main gnu machine:

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

Here are the compressed diffs against 2.2.2 and the complete sources  
(smallest first):

ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4.tar.lzma
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.2-2.2.4.diff.gz
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4.tar.bz2
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4.tar.gz

Here are the gpg detached signatures:

ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4.tar.lzma.sig
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.2-2.2.4.diff.gz.sig
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4.tar.bz2.sig
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4.tar.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.4.tar.lzma.sig

Here are the MD5 and SHA1 checksums:

	b93e00c31ac13915da66f2aec3404f9a  libtool-2.2.4.tar.lzma
	d25ce06681dbd7500a9a72b6d9d716af  libtool-2.2.2-2.2.4.diff.gz
	bbb81648164c48361e3fd0e1a058dc93  libtool-2.2.4.tar.bz2
	0b87e84c7aad3b5e979bbe35312fd4c1  libtool-2.2.4.tar.gz
5f1e7de0a0a285fcd2e921dcc060385d0395c1e8  libtool-2.2.4.tar.lzma
ef8b9271dc71ab1aad69c3d1dd04b45fa3f39aa6  libtool-2.2.2-2.2.4.diff.gz
bc485fd07c8b12820234240e9ef41dba693af2b7  libtool-2.2.4.tar.bz2
b00a18f3e7a7cbd7311e80d614564762d449074a  libtool-2.2.4.tar.gz

You can apply the diff to a freshly unpacked libtool-2.2.2  
distribution using GNU patch:

$ tar zxvf libtool-2.2.2.tar.gz
$ cd libtool-2.2.2
$ gzip -c ../libtool-2.2.2-2.2.4.diff.gz | patch -p1

You may need to rebootstrap the newly patched libtool tree as  
described below, since the timestamps of generated files will have  
been changed by GNU patch.

This release was bootstrapped with Autoconf 2.61 and Automake 1.10.1,  
but should be useable with any reasonably modern equivalents in your  
own projects.

Alternatively, you can fetch the unbootstrapped source code from git  
using the following commands:

$ git clone git://git.sv.gnu.org/libtool.git
$ cd libtool
$ git checkout v2.2.4

If there is demand we may enable pserver emulation from the git  
repository to reenable cvs checkouts like this:

$ cvs -z3 -d :pserver:[email protected]:/libtool.git co  
-r v2.2.4 -d libtool master

In either case, you will then need to have the latest release versions  
of Automake (1.10.1) and Autoconf (2.61) installed to bootstrap the  
checked out sources yourself.

Please report bugs to <[email protected]>, 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.

Enjoy!

  The Libtool Team
-- 
   ())_.              Email me: [email protected]
   ( '/           Read my blog: http://blog.azazil.net
   / )=         ...and my book: http://sources.redhat.com/autobook
`(_~)_