newsGNU Libtool - News: libtool-2.4.5 released [stable]

Latest News
GNU libtool-2.4.6 released [stable] posted by gary, Sun 15 Feb 2015 08:59:52 PM UTC - 0 replies
GNU libtool-2.4.5 released [stable] posted by gary, Mon 19 Jan 2015 05:11:26 PM UTC - 0 replies
GNU libtool-2.4.4 released [stable] posted by gary, Sat 29 Nov 2014 06:21:33 PM UTC - 0 replies
GNU libtool 2.4.3 released [stable] posted by gary, Mon 27 Oct 2014 08:11:41 PM UTC - 0 replies
libtool- released [alpha] posted by gary, Sun 27 Oct 2013 12:51:14 AM UTC - 0 replies
[Submit News]
[16 news in archive]

GNU libtool-2.4.5 released [stable]

Item posted by Gary V. Vaughan <gary> on Mon 19 Jan 2015 05:11:26 PM UTC.


The Libtool Team is pleased to announce the release of libtool 2.4.5.

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 bugfix release and a recommended upgrade for all users. Most
likely, this will be the last release that supports copying the libltdl
sources directly into your project -- libltdl is widely deployed now, and
there is absolutely no reason to give it special treatment compared to
any other library a project depends on.

Here are the compressed sources: (1.7MB) (952KB)

Here are the GPG detached signatures[*]:

Use a mirror for higher download bandwidth:

[*] Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact. First, be sure to download both the .sig file
and the corresponding tarball. Then, run a command like this:

gpg --verify libtool-2.4.5.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 --recv-keys 151308092983D606

and rerun the 'gpg --verify' command.

This release was bootstrapped with the following tools:
Autoconf 2.69
Automake 1.15
Gnulib v0.1-336-g342d9f0


  • Noteworthy changes in release 2.4.5 (2015-01-19) [stable]
    • New features:

- Libtoolize searches for the best available M4 on the user PATH at
runtime, rather than settling for the first one found.

- Support munging sys_lib_dlsearch_path_spec with LT_SYS_LIBRARY_PATH
environment variable.

    • Bug fixes:

- Bail out at configure time if the installed M4 is not sufficient
for the purposes of libtoolize.

- freebsd-elf library versioning was upgraded incorrectly in 2.4.4,
but now works properly again.

- Fix a 2.4.4 regression so that libltdl subprojects do not warn
about missing libltdl/libltdl directory as in prior releases.

- When using Sun C++ on Solaris or GNU/Linux we used to set libtool's
postdeps permanently, based on the contents of $CXX and $CXXFLAGS at
configure time, which was brittle and error-prone. Now, we no
longer check for a SunCC ABI at configure time, but augment the
postdeps at libtool time based on the current invocation flags on
each call.

    • Changes in supported systems or compilers:

- /usr/local prefixed rpaths are now added to the link-line on
ia64-hp-hpux*, because the default system runtime loader path does
not contain them.

- Previously, when using Sun C++ on Solaris or GNU/Linux, `-Cstd -Crun`
flags were added to $postdeps unless CXX or CXXFLAGS contained
`-library=stlport4`. Newer releases have added other compiler flags
that are also incompatible with `-Cstd -Crun`, so now we don't add
them if any of `-std=c++[0-9][0-9]`, `-library=stdcxx4` or
`-compat=g` were found in CXX or CXXFLAGS when the Sun C++ compiler
is detected.



No messages in GNU libtool-2.4.5 released [stable]


Back to the top

Powered by Savane 3.1-cleanup1