newsGNU Libtool - News: GNU Libtool 2.4.2 released [stable]

 
 
Latest News
libtool-2.4.7 released [stable] posted by growpotkin, Thu 17 Mar 2022 04:32:13 AM UTC
GNU libtool-2.4.6 released [stable] posted by gary, Sun 15 Feb 2015 08:59:52 PM UTC
GNU libtool-2.4.5 released [stable] posted by gary, Mon 19 Jan 2015 05:11:26 PM UTC
GNU libtool-2.4.4 released [stable] posted by gary, Sat 29 Nov 2014 06:21:33 PM UTC
GNU libtool 2.4.3 released [stable] posted by gary, Mon 27 Oct 2014 08:11:41 PM UTC

GNU Libtool 2.4.2 released [stable]

Item posted by Gary V. Vaughan <gary> on Tue 18 Oct 2011 09:59:19 AM UTC.

Libtoolers!

The Libtool Team is pleased to announce the release of GNU Libtool 2.4.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 release contains bugfixes accumulated over the last 13 months since
the release of 2.4 in September 2010.

New in 2.4.2 2011-10-17:

  • New features:


  - The --with-pic configure option now supports a list of comma-separated
    package names.  This can be used to build some static libraries with PIC
    objects while building others with non-PIC objects.

  - Initial support for Go, using the gccgo compiler.

  - On Mac OS X .dylib is now tried as well as .so with
    lt_dlopenext().

  • Bug fixes:


  - The generic approximation of the command line length limit (when getconf is
    not available) works again.  Regression introduced in v2.2.6-39-g9c3d4d8.
  - The bug that leaked developer tool paths into the release tarballs
    from ./bootstrap is fixed.
  - Improved support for the Cuda Compiler Driver (nvcc) on Darwin.
  - For GCC LTO support, the -fuse-linker-plugin switch is now also removed
    when computing compiler postdeps.

  • Important incompatible changes:


  - The undocumented hardcode_libdir_flag_spec_ld tag variable has been
    removed in favor of using hardcode_libdir_flag_spec with $wl set to empty.

  • Changes in supported systems or compilers:


  - Fixes for gfortran on Darwin, XL Fortran on GNU/Linux.
  - Support for FreeBSD 1.x (outdated since 1994) has been removed.


libtool-2.4.2 is available now from ftp.gnu.org, along with compressed diffs
against libtool-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.4.2.tar.gz (2.51MiB)
  ftp://ftp.gnu.org/gnu/libtool/libtool-2.4.2.tar.xz (0.82MiB)

Here are the compressed diffs against libtool-2.4:

  ftp://ftp.gnu.org/gnu/libtool/libtool-2.4-2.4.2.diff.gz (353.7KiB)

Here are the gpg detached signatures:

  ftp://ftp.gnu.org/gnu/libtool/libtool-2.4.2.tar.gz.sig (4.0KiB)
  ftp://ftp.gnu.org/gnu/libtool/libtool-2.4.2.tar.xz.sig (4.0KiB)
  ftp://ftp.gnu.org/gnu/libtool/libtool-2.4-2.4.2.diff.gz.sig (4.0KiB)

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

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

Here are the MD5 and SHA1 checksums:

  d2f3b7d4627e69e13514a40e72a24d50 libtool-2.4.2.tar.gz
  2ec8997e0c07249eb4cbd072417d70fe libtool-2.4.2.tar.xz
  676723ef67a060566aa9aab0cde60463 libtool-2.4-2.4.2.diff.gz
  22b71a8b5ce3ad86e1094e7285981cae10e6ff88 libtool-2.4.2.tar.gz
  4671f3323f2fbc712a70afce57602ce906a82a15 libtool-2.4.2.tar.xz
  87537042205aecac8c887cb3f9b03d6a2f28855e libtool-2.4-2.4.2.diff.gz

This release was bootstrapped with autoconf-2.68 and automake-1.11.1, but is
useable with autoconf-2.62 and automake-1.9.6 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.4.2

You will then need to have the latest release versions of Automake
(automake-1.11.1) and Autoconf (autoconf-2.68) installed to
bootstrap the checked out sources yourself.

Please report bugs to <bug-libtool@gnu.org>, 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!

 

Back to the top

Powered by Savane 3.13-cf05.
Corresponding source code