The Libtool Team is pleased to announce the release of GNU Libtool 1.5.2.
GNU Libtool hides the complexity of using shared libraries behind a consistent, portable interface. GNU Libtool ships with GNU libltdl, which hides the comlexity of loading dynamic runtime libraries (modules) behind a consistent, portable interface.
This release fixes bugs and annoyances present in the 1.5 release.
New in 1.5.2: 2004-01-25
* lt_dlrealloc is an official part of the libltdl API. * --tag, --silent and --debug options are preserved and reused when libtool calls itself for relinking etc. * `-pthread' and similar options are honoured when linking shared libraries. * -no-suppress in compile mode shows compiler output for both PIC and non-PIC object compilation. * New link mode option `-precious-files-regex' to prevent accidental removal of files you want to keep, such as test coverage data, from the temporary output directory. * Directories specified in /etc/ld.so.conf are no longer hardcoded on Linux. * Recognises the 'R' symbol type on Solaris so read-only symbols can be exported. * Bug fixes.
libtool-1.5.2 is available now from ftp.gnu.org, along with diffs and xdeltas against libtool-1.5 that are also available 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:
ftp://ftp.gnu.org/gnu/libtool/libtool-1.5.2.tar.gz
Here are the xdeltas and diffs against libtool-1.5:
ftp://ftp.gnu.org/gnu/libtool/libtool-1.5-1.5.2.diff.gz ftp://ftp.gnu.org/gnu/libtool/libtool-1.5-1.5.2.xdelta
Here are the gpg detached signatures:
ftp://ftp.gnu.org/gnu/libtool/libtool-1.5.2.tar.gz.sig ftp://ftp.gnu.org/gnu/libtool/libtool-1.5-1.5.2.diff.gz.sig ftp://ftp.gnu.org/gnu/libtool/libtool-1.5-1.5.2.xdelta.sig
Here are the MD5 and SHA1 checksums:
db66ba05502f533ad0cfd84dc0e03bd5 libtool-1.5.2.tar.gz cb66ad829b082cc5fdd9a99b2315e390 libtool-1.5-1.5.2.diff.gz 1df023f4893bb8cc77acf843250b5d38 libtool-1.5-1.5.2.xdelta d6f1e8fb544d71b3c88fb959521b34b9b6290260 libtool-1.5.2.tar.gz c6624106bf83517c923500ca215744901fec2070 libtool-1.5-1.5.2.diff.gz 63918920176c20e999abc06860d82fee58cabda8 libtool-1.5-1.5.2.xdelta
This release was bootstrapped with Autoconf 2.59 and Automake 1.8.2, but is useable with Autoconf 2.50 & later and Automake 1.4 & later in your own projects.
Alternatively, you can fetch the unbootstrapped sourcecode from anonymous cvs by using the following commands (just hit return when you are prompted for the password):
$ cvs -z3 -d :pserver:anoncvs@xxxxxxxxxxxxxxxxxxx:/cvsroot/libtool login
Password:
$ cvs -z3 -d :pserver:anoncvs@xxxxxxxxxxxxxxxxxxx:/cvsroot/libtool \
co -r release-1-5-2 libtool
You will then need to have the latest release versions of Automake and Autoconf installed to bootstrap the checked out sources yourself.
Please report bugs to <bug-libtool@xxxxxxx>.
Hi all,
For the OS QNX Neutrino the "host-os" name have to be tested, in the macro file acinclude.m4, not as "nto-qnx" but as "nto-qnx*". The "host-os" name in the OS QNX NTO depends on the version of the OS. In the OS QNX NTO v. 6.2.0, the "host-os" name is "nto-qnx6.2.0" and in v. 6.2.1, the "host-os" name is "nto-qnx6.2.1". Without this change, libtool will not be generate shared libraries under the OS QNX Neutrino. In previous versions the "host-os" name is "nto-qnx".
This problem is more complicated, because the "host-os" name depends on under how OS configure script was builded. I do not why. If I build the configure script under OS QNX NTO and run it, the "host-os" name have to be tested as "nto-qnx*". If I port a project from the OS Linux to the OS QNX NTO, sometimes the "host-os" name is "nto-qnx" only.
Milan
