GNU Libtool 2.2 released.

[Gary V. Vaughan]

If you have an expensive bottle of champagne saved for a very special
occasion, now might be a good time to break it open...

Following almost 4 grueling years in development, the Libtool Team is
pleased to announce the final release of GNU Libtool 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 stable release from the Libtool 2.2 branch.
Libtool 2.0 was never released, as by the time 1.9f was released
from the stable branch, the head of the development branch had
already become much more stable than the supposed stable branch!!

Compared to the old stable Libtool 1.5.x branch, the new stable 2.2
branch has been almost entirely rewritten, and has too many improvements
and brand new features to enumerate here.  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 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 sources (smallest first):

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

Here are the gpg detached signatures:

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

  3036f2b0159feb01abd202bca7f53f77  libtool-2.2.tar.lzma
  10c4ccc52b130153f7e7503fc7f769a4  libtool-2.2.tar.bz2
  217e9ec3e3cbdf891cbd4772140964a1  libtool-2.2.tar.gz
  d27da89b10bc0a285ebd9da88fd513d1d43c6f73  libtool-2.2.tar.lzma
  c257134336130d741182c8443683d6f89b391801  libtool-2.2.tar.bz2
  39935aaa8e4b80d7844af9ed7dd33b1da9bfd36a  libtool-2.2.tar.gz

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