GNU libtool 2.2.10 released (stable)

[Gary V. Vaughan]

Libtoolers!

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.

Here are the compressed sources:

  ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.10.tar.gz (2.3MB)
  ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.10.tar.lzma (772KB)

Here are the diffs against libtool 2.2.8:

  ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.8-2.2.10.diff.gz (24.0KB)

Here are the GPG detached signatures[1]:

  ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.10.tar.gz.sig (4.0KB)
  ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.10.tar.lzma.sig (4.0KB)
  ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.8-2.2.10.diff.gz.sig (4.0KB)

Here are the MD5 and SHA1 checksums[2]:

  b745d220e88163fcd9eea0a90ccf21b0          libtool-2.2.10.tar.gz
  2eba13ecd07653d0e34d4efe8e2974d8          libtool-2.2.10.tar.lzma
  515ca9770a1312bc303a95b3b1b99ab3          libtool-2.2.8-2.2.10.diff.gz
  e8fa9813d8e9a5497c636744e6fd3f55d86eec38  libtool-2.2.10.tar.gz
  f494f82e9f73c0679a76d077b9b54aef2a7bb610  libtool-2.2.10.tar.lzma
  e0f619256a1dc52a0f50a9423f5942311dfe344d  libtool-2.2.8-2.2.10.diff.gz

To reduce load on the main server, please one of the mirrors listed at:

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

[1] You can use the above signature files to verify that the
    corresponding file (without the .sig suffix) is the same
    file that was released by the owner of it's GPG key ID.
    First be sure to download both the .sig file and the
    corresponding file. Then run a cammand like this:

      gpg --verify libtool-2.2.10.tar.gz.sig

    If that command fails because you don't have the required
    public key, then run this command to import it:

      gpg --keyserver keys.gnupg.net --recv-keys 2983D606

    and rerun the `gpg --verify' command.

[2] You can use either of the above checksum files to verify
    that the corresponding file is complete and correct. To
    confirm that the file you downloaded has a checksum that
    matches the release note, compare it against the output
    one of the following commands:

      md5sum libtool-2.2.10.tar.gz
      shasum libtool-2.2.10.tar.gz

    (the name of the command sometimes varies between
    different operating systems).

New in 2.2.10 2010-06-10: git version 2.2.9a, Libtool team:

     NEWS (2.2.8): BlueGene compiler tests were performed on BG/P
     Fix a typo in the 2.2.8 release notes.
     Simplify license variations, and add missing license texts.
     Don't try the MSYS libdir path on MinGW.
     Rewrite manual intro to be gender-neutral.
     Fix versioning test for LDFLAGS=-Wl,--as-needed.
     Make versioning test stricter for w32, enable shared libs.
     Avoid autom4te warning about unnamed diversion.
     Fix testsuite helper macros to not hide failure.

Enjoy!