GNU Libtool 2.2.2 released.

[Gary V. Vaughan]

If you have some flat champagne left from the expensive bottle you
broke open for libtool-2.2, now might be a good time to finish it off...

Following more than 4 grueling weeks in development, the Libtool Team is
pleased to announce the release of GNU Libtool 2.2.2.

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 the first maintenance release from the Libtool 2.2 branch.

Compared to last month's Libtool 2.2 release, the new 2.2.2 has fixed
a regression and other assorted bugs.  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.2 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 and the complete
sources (smallest first):

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

Here are the gpg detached signatures:

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

Here are the MD5 and SHA1 checksums:

 5ba34d51d6207ac770be355396eab2e1  libtool-2.2-2.2.2.diff.gz
 0ea5dfadf233a5125d2b063136e6afaf  libtool-2.2.2.tar.lzma
 1c98a340bf172c3d76ef5440584657e6  libtool-2.2.2.tar.bz2
 9281a5f1976da110be872b1ba048d8ac  libtool-2.2.2.tar.gz
 df8be40b1b9d5c7155337ee83c0285f9a9a932aa  libtool-2.2-2.2.2.diff.gz
 caa12d097722c08d5994adc97d71eb1c56968d1c  libtool-2.2.2.tar.lzma
 a7ce88fc92411380081fd47d3197e7d539755365  libtool-2.2.2.tar.bz2
 41e0d829188083ab9f6bedf2b9eca89543dc0f8a  libtool-2.2.2.tar.gz

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

 $ tar zxvf libtool-2.2.tar.gz
 $ cd libtool-2.2
 $ gzip -c ../libtool-2.2-2.2.2.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
anonymous cvs by using the following command:

$ cvs -z3 -d :pserver:address@hidden:/sources/libtool \
  co -r release-2-2 libtool

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 <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.

Enjoy!

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

PGP.sig
Description: This is a digitally signed message part