Howdy, Libtoolers!
After a long hiatus, the Libtool Team is pleased to announce the release of
libtool 2.4.7.
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:
https://ftpmirror.gnu.org/libtool/libtool-2.4.7.tar.gz (1.9MB)
https://ftpmirror.gnu.org/libtool/libtool-2.4.7.tar.xz (996KB)
Here are the GPG detached signatures[*]:
https://ftpmirror.gnu.org/libtool/libtool-2.4.7.tar.gz.sig
https://ftpmirror.gnu.org/libtool/libtool-2.4.7.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
Here are the SHA1 and SHA256 checksums:
d3f2d5399f4bf5cbd974b812ebaca28d6492ca65 libtool-2.4.7.tar.gz
BOlsJATqcMWQxUbrpCAqThJyLGQAFsErmy8c49SB6ag libtool-2.4.7.tar.gz
0c90f1b046ea9cd7b32a4b5a6a9df4b46ddb637a libtool-2.4.7.tar.xz
T38hfwV85lX/IlWa0iGg/Y74StH8X8tpkM7MMzqhY10 libtool-2.4.7.tar.xz
The SHA256 checksum is base64 encoded, instead of the
hexadecimal encoding that most checksum tools default to.
[*] 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.7.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 6EAC957F8EEB55C0
and rerun the 'gpg --verify' command.
This release was bootstrapped with the following tools:
Autoconf 2.69
Automake 1.16.3
Gnulib a5218207e5
NEWS
* Noteworthy changes in release 2.4.7 (2022-03-16) [stable]
** New features:
- Libtool script now supports (configure-time and runtime) ARFLAGS
variable, which obsoletes AR_FLAGS. This is due to naming conventions
among other *FLAGS and to be consistent with Automake's ARFLAGS.
- Gnulib testsuite is enabled and run during 'make check'.
- Support the Windows version of the Intel C Compiler (icl) in
libtool script.
- Pass '-fsanitize=*' flags for GCC and LLVM, and '-specs=*' for GCC
to linker.
- Pass '-Xassembler=*' and '-Wa,*' flag to compilers and linkers.
- The variable 'FILECMD' with default value of '/usr/bin/file' was used to
replace existing hard coded references to '/usr/bin/file'.
- Add MidnightBSD support.
** Important incompatible changes:
- Libtool changed ARFLAGS/AR_FLAGS default from 'cru' to 'cr'.
- Do not pass '-pthread' to Solaris linker.
- 'libtool' and 'libtoolize' scripts now use '#! /usr/bin/env sh' shebang.
Previously '#! /bin/sh' was used, which presents challenges for
containerized environments.
** Bug fixes:
- Fix significant slowdown of libtoolize for certain projects (regression
introduced in 2.4.3 release) caused by infinite m4 macro recursion.
- Mitigate the slowdown of libtool script (introduced in v2.4.3) caused by
increased number of calls to '$SED $sed_quote_subst' (bug#20006).
- Properly parse and export TLS symbols on AIX.
- Various bug fixes surrounding use of 'sed'.
- Darwin systems set proper "allow undefined" flag on OSX 11, and
PowerPC 10.5.
- Removed some deprecated tests related to 'Makefile.inc' files.
Enjoy!
Libtoolers!
The Libtool Team is pleased to announce the release of libtool 2.4.6.
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
importantly, it regains most of the speed of 2.4.2 by correcting one of
two known regressions that were causing noticable slow-down when building
projects with many source files.
Here are the compressed sources:
http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.gz (1.7MB)
http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.xz (952KB)
Here are the GPG detached signatures[*]:
http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.gz.sig
http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.xz.sig
Use a mirror for higher download bandwidth:
http://www.gnu.org/order/ftp.html
[*] 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.6.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 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
NEWS
** New features:
- LT_SYS_LIBRARY_PATH can be set in config.site, or at configure time
and persists correctly in the generated libtool script.
** Bug fixes:
- Fix a race condition in ltdl dryrun test that would cause spurious
random failures of that test.
- LT_SYS_DLSEARCH_PATH is munged correctly.
Enjoy!
Libtoolers!
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:
http://ftpmirror.gnu.org/libtool/libtool-2.4.5.tar.gz (1.7MB)
http://ftpmirror.gnu.org/libtool/libtool-2.4.5.tar.xz (952KB)
Here are the GPG detached signatures[*]:
http://ftpmirror.gnu.org/libtool/libtool-2.4.5.tar.gz.sig
http://ftpmirror.gnu.org/libtool/libtool-2.4.5.tar.xz.sig
Use a mirror for higher download bandwidth:
http://www.gnu.org/order/ftp.html
[*] 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 keys.gnupg.net --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
NEWS
** 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.
Enjoy!
Libtoolers!
The Libtool Team is pleased to announce the release of libtool 2.4.4.
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 to clean-up some of the small issues in 2.4.3
for which you kindly provided patches. There are still some known (and
unknown!) regressions, especially on unusual platforms. Patches to fix
those are not only welcome, but necessary to keep Libtool working in
those places.
Here are the compressed sources:
http://ftpmirror.gnu.org/libtool/libtool-2.4.4.tar.gz (1.7MB)
http://ftpmirror.gnu.org/libtool/libtool-2.4.4.tar.xz (936KB)
Here are the GPG detached signatures[*]:
http://ftpmirror.gnu.org/libtool/libtool-2.4.4.tar.gz.sig
http://ftpmirror.gnu.org/libtool/libtool-2.4.4.tar.xz.sig
Use a mirror for higher download bandwidth:
http://www.gnu.org/order/ftp.html
[*] 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.4.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 151308092983D606
and rerun the 'gpg --verify' command.
This release was bootstrapped with the following tools:
Autoconf 2.69
Automake 1.14.1
Gnulib v0.1-270-g1b6c775
NEWS
** New features:
- Libltdl maintains its own fork of argz, with macros and files in
the LT_ and lt__ namespaces (resp.) where they cannot clash with
client projects' use of gnulib argz.
** Bug fixes:
- Installation of 'libtoolize' once again obeys '--program-prefix',
'--program-suffix' and '--program-transform-name' configure options.
- `libtoolize` doesn't remove any files that it can't reinstall,
including old versions of the snippet directory, and gnulib's
version of the argz module and supporting files.
- LT_FUNC_DLYSM_USCORE now works correctly on systems that don't
support self dlopen()ing.
** Important incompatible changes:
- LT_LIB_DLLOAD no longer prepends -ldl or -ldld to LIBS, causing
duplicate occurrences in libltdl link lines. If you need to
add a library for dlopen() or shl_load() in your Makefile, then
use $(LIBADD_DLOPEN) or $(LIBADD_SHL_LOAD) respectively. If you
are using libltdl, this all happens automatically, and the only
difference you'll see is no more duplicated library names in the
verbose link line.
** Changes in supported systems or compilers:
- Preliminary support for tcc on linux*. Although it already worked
sometimes in previous releases, making sure to set LD correctly now
avoids mis-matching GNU ld with tcc:
./configure CC=tcc LD=tcc
- Added -os2dllname option to work around 8 character base name
limit on OS/2. The option has no effect on other systems.
- Support for DLL versioning, -export-symbols and -export-symbols-regex
on OS/2.
- Support filename-based shared library versioning on AIX. See manual
for details.
Enjoy!
Libtoolers!
The Libtool Team is pleased to announce the release of libtool 2.4.3.
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 an interrim release with a few known small regressions, as yet
unfixed due to a lack of man-power. But rather than make you wait any
longer to enjoy the new features and cleaner build using the latest
autotools, gnulib, config.guess, config.sub and bootstrap scripts, with
support for several new systems and system revisions, we're releasing
it now in anticipation of your patches for the remaining nits and
corner-cases.
Here are the compressed sources:
http://ftpmirror.gnu.org/libtool/libtool-2.4.3.tar.gz (1.7MB)
http://ftpmirror.gnu.org/libtool/libtool-2.4.3.tar.xz (928KB)
Here are the GPG detached signatures[*]:
http://ftpmirror.gnu.org/libtool/libtool-2.4.3.tar.gz.sig
http://ftpmirror.gnu.org/libtool/libtool-2.4.3.tar.xz.sig
Use a mirror for higher download bandwidth:
http://www.gnu.org/order/ftp.html
[*] 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.3.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 151308092983D606
and rerun the 'gpg --verify' command.
This release was bootstrapped with the following tools:
Autoconf 2.69
Automake 1.14.1
Gnulib v0.1-234-g8415b67
NEWS
** New features:
- Moved to gnulib release infrastructure.
- M4 is now used for scanning the M4 macros in your configure.ac that
'libtoolize' looks at to determine what files you want, and where you
would like them installed. This means that you can compose your
version number or any other argument that Libtoolize needs to know at
M4 time using git-version-gen from gnulib, for example.
- Invoking 'libtoolize --ltdl' no longer maintains a separate autoconf
macro directory in the libltdl tree, but automatically adjusts the
installed libltdl configuration files to share whatever macro
directory is declared by the parent project. (Note: if you were
already sharing a macro directory with AC_CONFIG_MACRO_DIR(ltdl/m4)
or similar, that still works as does any other directory choice).
- Invoking 'libtoolize --ltdl' no longer maintains a separate auxiliary
scripts directory in the libltdl tree, but automatically adjusts the
installed libltdl configuration files to share whatever auxiliary
scripts directory is declared by the parent project. (Note: if you
were already sharing an auxiliary directory with subproject libltdl
using AC_CONFIG_AUX_DIR(ltdl/config) or similar, that still works as
does any other directory choice).
- The legacy tests have all been migrated to the Autotest harness.
- The Autotest testsuite can be run without the especially time consuming
tests with:
make check-local TESTSUITEFLAGS='-k "!expensive"'
** Bug fixes:
- Fix a long-standing latent bug in autom4te include path for autotests
with VPATH builds.
- Fix a long-standing latent bug in libtoolize that could delete lines
from libltdl/Makefile.am in recursive mode due to underquoting in a
sed script.
- Fix a long-standing bug in libtoolize, by outputting the 'putting
auxiliary files in' header with 'libtoolize --ltdl --subproject'.
- Fix a long-standing bug in libtoolize subproject installation, by not
installing a set of autoconf macro files into the parent project if
there is no configure.ac present to use them.
- The libtoolize subproject mode selector is now named '--subproject'
and is equivalent to the implied '--subproject' mode when no other
mode is selected; '--standalone' never worked, and is no longer
accepted.
- Libtool and libtoolize no longer choke on paths with a comma in them.
- In the case where $SHELL does not have the same enhanced features
(e.g. the ability to parse 'var+=append') as $CONFIG_SHELL, libtool
will now correctly fallback to using only vanilla shell features
instead of failing with a parse at startup.
- Correctly recognize import libraries when Microsoft dumpbin is used
as the name lister and extend the dumpbin wrapper to find symbols
in import libraries using the -headers option of dumpbin. Also fix a
bug in the dumpbin wrapper that could lead to broken symbol listings
in some corner cases.
- Use the improved Microsoft dumpbin support to mend preloading of
import libraries for Microsoft Visual C/C++.
- No longer mangle module-definition (.def) files when feeding them to
the Microsoft Visual C/C++ linker via the -export-symbols argument to
the libtool script, thus matching how .def files are handled when
using GNU tools.
- Recognize more variants (e.g. those starting with a LIBRARY statement)
of module-definitions (.def) files when using them instead of a raw
list of symbols to export.
- Fix a long-standing bug when using libtoolize without automake; we
no longer remove install-sh with --force, since it's not a file
libtoolize will reinstall without --install..
** Important incompatible changes:
- GNU M4 is required to run libtoolize in a directory with a
'configure.ac' (or 'configure.in') that needs tracing to determine
what modes and directories have been specified.
- The use of the idiosyncratically named 'Makefile.inc' in nonrecursive
libltdl builds is deprecated, although it will be supported for one
more year or until the next release, whichever takes longer. Please
upgrade to the more standard naming of 'ltdl.mk' in keeping with other
GNU projects.
- libtoolize now behaves consistenty in respect of multiple directory
arguments to ACLOCAL_AMFLAGS and multiple invocations of AC_CONFIG-
_MACRO_DIRS, where the first directory is always selected. Previous
releases took the first ACLOCAL_AMFLAGS argument, but the last
invocation of AC_CONFIG_MACRO_DIRS.
- The libtoolize program now advises use of the new Autoconf
AC_CONFIG_MACRO_DIRS declaration. If you follow that advice, all
your developers will need at least autoconf-2.70 and automake-1.13
to rebootstrap your probject. If you still need to support
bootstrap with older Autotools, then you should add the following
to your configure.ac file:
m4_ifndef([AC_CONFIG_MACRO_DIRS],
[m4_define([AC_CONFIG_MACRO_DIRS],
m4_defn([AC_CONFIG_MACRO_DIR]))])
- Overhead of probing for a non-backslash crippled echo equivalent
during initialization of every script has been removed in favor of
trusting that "printf %s\n" works out of the box on all non-museum
host architectures. Manually setting ECHO appropriately in the
build environment will be necessary on some ancient architectures.
** Changes in supported systems or compilers:
- Support for bitrig (--bitrig*).
- Solaris 7 and earlier requires ECHO=/usr/ucb/echo in the build
environment, to build and use libtool.
Enjoy!
Libtoolers!
The Libtool Team is pleased to announce the release of libtool 2.4.2.418.
This is a preliminary alpha release to begin platform testing in preparation
for the next stable release.
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://alpha.gnu.org/gnu/libtool/libtool-2.4.2.418.tar.gz (1.6MB)
ftp://alpha.gnu.org/gnu/libtool/libtool-2.4.2.418.tar.xz (920KB)
Here are the GPG detached signatures[*]:
ftp://alpha.gnu.org/gnu/libtool/libtool-2.4.2.418.tar.gz.sig
ftp://alpha.gnu.org/gnu/libtool/libtool-2.4.2.418.tar.xz.sig
Use a mirror for higher download bandwidth:
http://www.gnu.org/order/ftp.html
[*] 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.2.418.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.
This release was bootstrapped with the following tools:
Autoconf 2.69
Automake 1.14
Gnulib 5191b35
NEWS
** New features:
- Moved to gnulib release infrastructure.
- M4 is now used for scanning the M4 macros in your configure.ac that
'libtoolize' looks at to determine what files you want, and where you
would like them installed. This means that you can compose your
version number or any other argument that Libtoolize needs to know at
M4 time using git-version-gen from gnulib, for example.
- Invoking 'libtoolize --ltdl' no longer maintains a separate autoconf
macro directory in the libltdl tree, but automatically adjusts the
installed libltdl configuration files to share whatever macro
directory is declared by the parent project. (Note: if you were
already sharing a macro directory with AC_CONFIG_MACRO_DIR(ltdl/m4)
or similar, that still works as does any other directory choice).
- Invoking 'libtoolize --ltdl' no longer maintains a separate auxiliary
scripts directory in the libltdl tree, but automatically adjusts the
installed libltdl configuration files to share whatever auxiliary
scripts directory is declared by the parent project. (Note: if you
were already sharing an auxiliary directory with subproject libltdl
using AC_CONFIG_AUX_DIR(ltdl/config) or similar, that still works as
does any other directory choice).
- The legacy tests have all been migrated to the Autotest harness.
- The Autotest testsuite can be run without the especially time consuming
tests with:
make check-local TESTSUITEFLAGS='-k "!expensive"'
** Bug fixes:
- Fix a long-standing latent bug in autom4te include path for autotests
with VPATH builds.
- Fix a long-standing latent bug in libtoolize that could delete lines
from libltdl/Makefile.am in recursive mode due to underquoting in a
sed script.
- Fix a long-standing bug in libtoolize, by outputting the 'putting
auxiliary files in' header with 'libtoolize --ltdl --subproject'.
- Fix a long-standing bug in libtoolize subproject installation, by not
installing a set of autoconf macro files into the parent project if
there is no configure.ac present to use them.
- The libtoolize subproject mode selector is now named '--subproject'
and is equivalent to the implied '--subproject' mode when no other
mode is selected; '--standalone' never worked, and is no longer
accepted.
- Libtool and libtoolize no longer choke on paths with a comma in them.
- In the case where $SHELL does not have the same enhanced features
(e.g. the ability to parse 'var+=append') as $CONFIG_SHELL, libtool
will now correctly fallback to using only vanilla shell features
instead of failing with a parse at startup.
- Correctly recognize import libraries when Microsoft dumpbin is used
as the name lister and extend the dumpbin wrapper to find symbols
in import libraries using the -headers option of dumpbin. Also fix a
bug in the dumpbin wrapper that could lead to broken symbol listings
in some corner cases.
- Use the improved Microsoft dumpbin support to mend preloading of
import libraries for Microsoft Visual C/C++.
- No longer mangle module-definition (.def) files when feeding them to
the Microsoft Visual C/C++ linker via the -export-symbols argument to
the libtool script, thus matching how .def files are handled when
using GNU tools.
- Recognize more variants (e.g. those starting with a LIBRARY statement)
of module-definitions (.def) files when using them instead of a raw
list of symbols to export.
** Important incompatible changes:
- GNU M4 is required to run libtoolize in a directory with a
'configure.ac' (or 'configure.in') that needs tracing to determine
what modes and directories have been specified.
- The use of the idiosyncratically named 'Makefile.inc' in nonrecursive
libltdl builds is deprecated, although it will be supported for one
more year or until the next release, whichever takes longer. Please
upgrade to the more standard naming of 'ltdl.mk' in keeping with other
GNU projects.
- libtoolize now behaves consistenty in respect of multiple directory
arguments to ACLOCAL_AMFLAGS and multiple invocations of AC_CONFIG-
_MACRO_DIRS, where the first directory is always selected. Previous
releases took the first ACLOCAL_AMFLAGS argument, but the last
invocation of AC_CONFIG_MACRO_DIRS.
- The libtoolize program now advises use of the new Autoconf
AC_CONFIG_MACRO_DIRS declaration. If you follow that advice, all
your developers will need at least autoconf-2.70 and automake-1.13
to rebootstrap your probject. If you still need to support
bootstrap with older Autotools, then you should add the following
to your configure.ac file:
m4_ifndef([AC_CONFIG_MACRO_DIRS],
[m4_define([AC_CONFIG_MACRO_DIRS],
m4_defn([AC_CONFIG_MACRO_DIR]))])
** Changes in supported systems or compilers:
- Support for bitrig (--bitrig*).
Enjoy!
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:
- 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().
- 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.
- 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.
- 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!
Libtoolers!
The Libtool Team is pleased to announce the release of GNU Libtool 2.4.
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.
New in 2.4 2010-09-22:
- Sysroot support. This allows you to build cross-compiled packages
with the same prefix that will be used on the destination machine,
and still find dependent libraries under the compiler's "sysroot".
Without sysroot support, paths internal to the build system may leak
into the product of the build.
Sysroot support is disabled unless the --with-sysroot configure
option is passed to configure, because .la files generated with
sysroot support will not be usable in general with older Libtools.
- On non-cygwin Windows systems, we now lookup potential library
file names without regard to file name case.
- The old testsuite now uses the `parallel-tests' Automake test driver
now for more concurrency and better test logging. For this, tests are
run in verbose mode by default now.
- Autoconf 2.62 and Automake 1.11.1 or newer are now required for
bootstrapping Libtool. For using Libtool in your own projects,
Autoconf 2.59 and Automake 1.9.6 should still work.
- The fix_srcfile_path variable has been replaced by a more thorough
mechanism triggered by the to_tool_file_cmd variable.
- Initial support for the Microsoft C/C++ Compiler, with help from
the compile script in unreleased Automake 1.12. Override the manifest
tool used to embed the manifest resource through the environment
variable MANIFEST_TOOL. Please note that the import library naming
has changed (from foo-2.lib to foo.dll.lib) from when the code lived
in its own git branch.
- Initial support for the NAG Fortran compiler on GNU/Linux.
- The `check-interactive' and `check-noninteractive' convenience make
targets now also work for the old testsuite.
- Warnings from Autoconf v2.67-36-g1e604ec about incomplete programs
passed to AC_*_IFELSE tests have been fixed.
- On IRIX, the test for -Wl,-exported_symbol now also works with gfortran.
libtool-2.4 is available now from ftp.gnu.org, along with compressed diffs
against libtool-2.2.10. 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.tar.gz (2.5MiB)
ftp://ftp.gnu.org/gnu/libtool/libtool-2.4.tar.xz (883KiB)
Here are the compressed diffs against libtool 2.2.10:
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.10-2.4.diff.gz (655KiB)
Here are the gpg detached signatures:
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4.tar.gz.sig (4.0KiB)
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4.tar.xz.sig (4.0KiB)
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.10-2.4.diff.gz.sig (4.0KiB)RANCH@-@VERSION@.xdelta.sig
You should download the signature named after any tarball you download,
and then verify its integrity with, for example:
gpg --verify libtool-2.4.tar.gz.sig
Here are the MD5 and SHA1 checksums:
b32b04148ecdd7344abc6fe8bd1bb021 libtool-2.4.tar.gz
4e6144439d95d7332dc50ace6dd24c55 libtool-2.4.tar.xz
7bb66dc1df9d4e11160264847d905692 libtool-2.2.10-2.4.diff.gz
149e9d7a993b643d13149a94d07bbca1085e601c libtool-2.4.tar.gz
a5a44aa791c8b93cbe1c2f839368cd3de5f5f3e1 libtool-2.4.tar.xz
639b6c70f40c94d92c72cdad0381d5750ea41124 libtool-2.2.10-2.4.diff.gz
This release was bootstrapped with autoconf-2.67 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
You will then need to have the latest release versions of Automake
(automake-1.11.1) and Autoconf (autoconf-2.67) 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!
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!
Libtoolers!
The Libtool Team is pleased to announce the 2.2.8 release of GNU Libtool.
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.8.tar.gz (2.3MB)
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.8.tar.lzma (772KB)
Here are the diffs against libtool 2.2.6a:
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a-2.2.8.diff.gz (2.3MB)
Here are the GPG detached signatures[1]:
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.8.tar.gz.sig (4.0KB)
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.8.tar.lzma.sig (4.0KB)
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a-2.2.8.diff.gz.sig (4.0KB)
Here are the MD5 and SHA1 checksums[2]:
cad2a7188242bc8dbab0645532ae3d6f libtool-2.2.8.tar.gz
0aec086ee0cf01bb029701c20c0a0741 libtool-2.2.8.tar.lzma
be24f49690f0ed669b47d1c4d9b815e6 libtool-2.2.6a-2.2.8.diff.gz
e0fd6f9d39c81c2da8b548411c74a46c24442abf libtool-2.2.8.tar.gz
e160056cab3b0d31db6c929f12ddd4a77e2a024d libtool-2.2.8.tar.lzma
c0ad48a14e7413316ad05eaddf31048548437dbc libtool-2.2.6a-2.2.8.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.8.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.8.tar.gz
shasum libtool-2.2.8.tar.gz
(the name of the command sometimes varies between
different operating systems).
New in 2.2.8 2010-06-05:
- Libtool ships and installs man pages for libtool and libtoolize now.
- New libtool command line flag --help-all.
- New libtool command line flag --no-silent (with alternate spelling
--no-quiet). This flag (re)enables the default informational messages,
but has no effect on so-called "verbose" output messages.
- New libtool command line flag --no-verbose, which disables only
the extra "verbose" output messages and has no effect on the
default informational messages.
- New convenience make targets `check-noninteractive' to avoid long testsuite
runs on Windows with popup windows in the middle, and `check-interactive'
for the complement set of tests.
- New link mode flag -bindir to specify the location for installed PE DLLs.
- Wrapper scripts and wrapper executables for programs linked against
uninstalled shared libraries now support command-line options --lt-debug
and --lt-dump-script.
- The wrapper command line option support described above introduces the
following incompatibility: the wrapper will remove any command line
options that begin with '--lt-*' from the argument list before launching
(uninstalled) programs. Any '--lt-*' option on the command line not
recognized by the wrapper will result in an error.
- Improved support for 64bit Windows (mingw64).
- Improved support for cegcc (Windows CE/PocketPC).
- Support for GNU/kOpenSolaris (kopensolaris*-gnu).
- Initial support for compilers on BlueGene BG/L.
- Improved support for Atari FreeMiNT.
- With binutils 2.19.50+, shared libraries can be built on AIX.
- Initial support for the Cuda Compiler Driver on GNU/Linux.
- Support for Haiku (i586-pc-haiku).
- Fix 2.2.6 regression that prevented using the libltdl macros together
with Autoconf 2.59 (`possibly undefined macro: LT_LIBEXT').
- Fix 2.2.4 regression that caused arguments with special characters
to be mangled by the compile wrapper for uninstalled programs on MinGW.
- libtool command line flag --verbose now also enables explicit
verbose output, in addition to its previous behavior of (re)enabling
only the default informational output. See New Features, --no-silent.
- Link tests are guarded by cache variables so they can be avoided for
bootstrapping purposes (e.g., when link tests are not possible).
- Argument mangling of execute mode has been improved (i.e., lessened).
- Fix 2.1b regression that caused nm to not be the default name lister.
The regression affected mainly (arguably broken) cross compiles.
- Fix long standing bug that caused compiler checks for Fortran and
C++ compilers to run twice.
- Link mode works around a parallel build failure on Darwin 9.6.0 due
to the `ar' `flock'ing an archive upon extraction, by protecting the
extraction of convenience archives with a lock.
- The Libtool macro files do not contain instances of _oline_ any more,
easing merges for configure scripts that are added to version control.
- Fix ancient bug where "-Wc," was turned into "$wl" (typically "-Wl,")
when using the compiler driver to link programs. Now "-Wc," is stripped
just as it is when linking libraries through the compiler driver.
- Symbol versioning works with the GNU gold linker now.
- Fixes for detection of shared library dependencies on MinGW systems.
- Fixed Sun compiler detection on Solaris with sunCC, sunf77 etc. names.
- The manual is distributed under the terms of the GNU FDL 1.3 now.
Enjoy!
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.
The Libtool Team is pleased to announce release candidate 2.2.7b of GNU
Libtool. If there are no serious deficiencies reported in this release,
it will be renumbered as 2.2.8 and re-released (otherwise, we'll fix
any problems and put out 2.2.7d first).
Here are the compressed sources:
ftp://alpha.gnu.org/gnu/libtool/libtool-2.2.7b.tar.gz
ftp://alpha.gnu.org/gnu/libtool/libtool-2.2.7b.tar.lzma
Here are the diffs against libtool-2.2.6a:
ftp://alpha.gnu.org/gnu/libtool/libtool-2.2.6a-2.2.7b.diff.gz
Here are the gpg detached signatures:
ftp://alpha.gnu.org/gnu/libtool/libtool-2.2.7b.tar.gz.sig
ftp://alpha.gnu.org/gnu/libtool/libtool-2.2.7b.lzma.sig
ftp://alpha.gnu.org/gnu/libtool/libtool-2.2.6a-2.2.7b.diff.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.7b.tar.gz.sig
Here are the MD5 and SHA1 checksums:
9f66a85efaeed0d9652f647986f6ad5b libtool-2.2.7b.tar.gz
865d99837c72d7b8f599a9bf5d85f4c7 libtool-2.2.7b.tar.lzma
3ddf3c1e9d0ff3aa16c5dc5328a58d6e libtool-2.2.6a-2.2.7b.diff.gz
6cf7bb650bcd93e89c86c685924f08656cb00f62 libtool-2.2.7b.tar.gz
f6038e00be29557f34948731d33b5e779b0d92df libtool-2.2.7b.tar.lzma
df42829d81dfead788c858cb2cfb76f388506e2e libtool-2.2.6a-2.2.7b.diff.gz
This release has much improved support for Windows based platforms, as
well as a selection of incremental changes, new features and a plethora
of bug fixes.
This release was bootstrapped with autoconf-2.65 and automake-1.11.1,
but is useable with any reasonably modern autotools (or, indeed, entirely
without autotools!) 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.2.7b
You will then need to have recent versions of Automake and Autoconf
installed to bootstrap the checked out sources yourself.
New in 2.2.7b: 2010-05-20
- Libtool ships and installs man pages for libtool and libtoolize now.
- New libtool command line flag --help-all.
- New libtool command line flag --no-silent (with alternate spelling
--no-quiet). This flag (re)enables the default informational messages,
but has no effect on so-called "verbose" output messages.
- New libtool command line flag --no-verbose, which disables only
the extra "verbose" output messages and has no effect on the
default informational messages.
- New convenience make targets `check-noninteractive' to avoid long testsuite
runs on Windows with popup windows in the middle, and `check-interactive'
for the complement set of tests.
- New link mode flag -bindir to specify the location for installed PE DLLs.
- Wrapper scripts and wrapper executables for programs linked against
uninstalled shared libraries now support command-line options --lt-debug
and --lt-dump-script.
- The wrapper command line option support described above introduces the
following incompatibility: the wrapper will remove any command line
options that begin with '--lt-*' from the argument list before launching
(uninstalled) programs. Any '--lt-*' option on the command line not
recognized by the wrapper will result in an error.
- Improved support for 64bit Windows (mingw64).
- Improved support for cegcc (Windows CE/PocketPC).
- Support for GNU/kOpenSolaris (kopensolaris*-gnu).
- Initial support for compilers on BlueGene BG/L.
- Improved support for Atari FreeMiNT.
- With binutils 2.19.50+, shared libraries can be built on AIX.
- Initial support for the Cuda Compiler Driver on GNU/Linux.
- Support for Haiku (i586-pc-haiku).
- Fix 2.2.6 regression that prevented using the libltdl macros together
with Autoconf 2.59 (`possibly undefined macro: LT_LIBEXT').
- Fix 2.2.4 regression that caused arguments with special characters
to be mangled by the compile wrapper for uninstalled programs on MinGW.
- libtool command line flag --verbose now also enables explicit
verbose output, in addition to its previous behavior of (re)enabling
only the default informational output. See New Features, --no-silent.
- Link tests are guarded by cache variables so they can be avoided for
bootstrapping purposes (e.g., when link tests are not possible).
- Argument mangling of execute mode has been improved (i.e., lessened).
- Fix 2.1b regression that caused nm to not be the default name lister.
The regression affected mainly (arguably broken) cross compiles.
- Fix long standing bug that caused compiler checks for Fortran and
C++ compilers to run twice.
- Link mode works around a parallel build failure on Darwin 9.6.0 due
to the `ar' `flock'ing an archive upon extraction, by protecting the
extraction of convenience archives with a lock.
- The Libtool macro files do not contain instances of _oline_ any more,
easing merges for configure scripts that are added to version control.
- Fix ancient bug where "-Wc," was turned into "$wl" (typically "-Wl,")
when using the compiler driver to link programs. Now "-Wc," is stripped
just as it is when linking libraries through the compiler driver.
- Symbol versioning works with the GNU gold linker now.
- Fixes for detection of shared library dependencies on MinGW systems.
- Fixed Sun compiler detection on Solaris with sunCC, sunf77 etc. names.
- The manual is distributed under the terms of the GNU FDL 1.3 now.
Enjoy!
The Libtool Team
We are pleased to announce the release of GNU Libtool 2.2.6b.
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 is a bug fix release for version 2.2.6. The following
bugs are fixed:
- Fixed libltdl to no longer attempt to dlopen() the old_library
listed in the .la file. Now will use only the preopen loader to
attempt to load it. This may be a security issue, all users are
advised to upgrade.
- Similarly, don't open module.la from the current directory, this
changes the behavior of libltdl to match the documentation.
libtool-2.2.6b is available now from ftp.gnu.org, along with diffs
against libtool-2.2.6a. 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.2.6b.tar.gz
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6b.tar.lzma
Here are the diffs against libtool-2.2.6a:
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a-2.2.6b.diff.gz
The MD5 and SHA1 checksums are:
libtool-2.2.6b.tar.gz 07da460450490148c6d2df0f21481a25
libtool-2.2.6b.tar.lzma a4b36980765003b47dd75ac9429f4f11
libtool-2.2.6a-2.2.6b.diff.gz a485788eb8fac09f7bb19b9f471ecf16
libtool-2.2.6b.tar.gz 5afa73c8ef9ebe64bbb438a0f8779c9036e43c55
libtool-2.2.6b.tar.lzma 18baaac89eed8be7bd2af2d2181598e176029cc6
libtool-2.2.6a-2.2.6b.diff.gz 161b4f775d2e17890a25fd791c2deb3a69dcf293
This release was bootstrapped with automake-1.11 and autoconf-2.64.
You can fetch the unbootstrapped source code with git by using the
following commands:
$ git clone git://git.savannah.gnu.org/libtool.git
$ cd libtool
$ git checkout v2.2.6b
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.
I'm embarrassed to announce the release of GNU Libtool 2.2.6a.
This release is identical to yesterday's 2.2.6 release, except that I've calculated the libltdl version number correctly. I was
overzealous about the library interface changes, and released 2.2.6 to build libltdl.so.9 as it's soname (making it incompatible with earlier releases from the 2.2 branch using libltdl.so.7).
My theory was that we had removed some of the argz access points that were accidentally exported on non-GNU/Linux machines, that strictly would require a new soname. Since 2.2 is a maintenance branch, and since the removed access points were not documented and should not have been visible in any case, I've pulled the 2.2.6 release and tarballs from ftp.gnu.org, and replaced them with equivalent files named with `2.2.6a'. The mirrors should catch up shortly.
When built and installed, the 2.2.6a libtool releases will still be called 2.2.6 in the install tree, and are identical to yesterdays release in every way, with the exception of using the correct soname for libltdl, so that backwards compatibility with earlier stable 2.2 releases is not broken. To avoid confusion with the broken 2.2.6 tarballs, I've simple changed the new filenames to use 2.2.6a.
A working libtool-2.2.6 is available now from ftp.gnu.org, along with diffs and against libtool-2.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.2.6a.tar.gz
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a.tar.lzma
Here are the diffs against libtool-2.2.4:
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4-2.2.6a.diff.gz
Here are the gpg detached signatures:
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a.tar.gz.sig
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a.tar.lzma.sig
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4-2.2.6a.diff.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.6a.tar.lzma.sig
Here are the MD5 and SHA1 checksums (note these are different to
yesterdays broken release):
8ca1ea241cd27ff9832e045fe9afe4fd libtool-2.2.6a.tar.gz
b121e4848cc53fdd69e796aed73b9ccf libtool-2.2.6a.tar.lzma
edbb99827bbfaa687f67cb75b77dff05 libtool-2.2.4-2.2.6a.diff.gz
7b547877b1b78b547343e4678a531aece8949904 libtool-2.2.6a.tar.gz
7c5fdce11777261a6c407fe97ac8a1ae5fe99d2b libtool-2.2.6a.tar.lzma
8fb591cc2e995b1ce14d95206e33df3cf611639e libtool-2.2.4-2.2.6a.diff.gz
This release was bootstrapped with autconf-2.62 and automake-1.10.1, but is useable with any reasonably modern equivalents 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.2.6a
You will then need to have the latest release versions of Automake (1.10.1) and Autoconf (2.62) 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.
Apologetically,
Gary
The Libtool Team is pleased to announce the release of GNU Libtool 2.2.6.
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 has support for some new compilers, and fixes a handful of small bugs present in the last release, as well as introducing a new libltdl API that prevents it from opening anything but preloaded modules.
libtool-2.2.6 is available now from ftp.gnu.org, along with
diffs and against libtool-2.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.2.6.tar.gz
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6.tar.lzma
Here are the diffs against libtool-2.2.4:
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4-2.2.6.diff.gz
Here are the gpg detached signatures:
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6.tar.gz.sig
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6.tar.lzma.sig
ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.4-2.2.6.diff.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.6.tar.lzma.sig
Here are the MD5 and SHA1 checksums:
1158d6b0535c2b9804e0fab01d80f8be libtool-2.2.6.tar.gz
1d82a7e523659f0b30c4624cf3e3af3c libtool-2.2.6.tar.lzma
07d1365b799aab9640c83f5e3bfd5772 libtool-2.2.4-2.2.6.diff.gz
0a85c645bcd77b4bca255edfc62c30398f6718ff libtool-2.2.6.tar.gz
6ecfe5594cfb8da7e3df6038b8b0c84aff0caef8 libtool-2.2.6.tar.lzma
62aee5b0a5acc2ffab917572e103302923cd4bce libtool-2.2.4-2.2.6.diff.gz
This release was bootstrapped with autconf-2.62 and automake-1.10.1, but is useable with any reasonably modern equivalents 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.2.6
You will then need to have the latest release versions of Automake (1.10.1) and Autoconf (2.62) 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!
The Libtool Team