[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU Libtool 1.5.23b released (alpha release).

From: haibin zhang
Subject: Re: GNU Libtool 1.5.23b released (alpha release).
Date: Sat, 24 Feb 2007 18:22:53 +0800 (CST)

HI ,
I have tested  1.5.23b in mingw in Windows XP, but I still find the bug of libtool.
The bug is :
If I build my project in directory same as source code directory, the built file can't be run.

for example:
I have a project named hbstock-2.0.8 and tar file : hbstock-2.0.8.tar.gz

if I do like this , the built binary file can work fine.
tar zxvf hbstock-2.0.8.tar.gz
mkdir build
cd build
../hbstock-2.0.8/configure --prefix=/opt/hbstock
make install

but if I do like this , the built binary file can't  run.

tar zxvf hbstock-2.0.8.tar.gz
cd hbstock-2.0.8
./configure --prefix=/opt/hbstock
make install

The built binary file can't run.

You can download hbstock-2.0.8.tar.gz from here to test this bug :


Ralf Wildenhues <address@hidden> 写道:
The Libtool Team would like to announce alpha release 1.5.23b of GNU

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:

Here are the xdeltas and diffs against libtool-1.5.22:

Here are the gpg detached signatures:

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

gpg --verify libtool-1.5.23b.tar.gz.sig

Here are the MD5 and SHA1 checksums:

d396433eca05ce2da9809e2af76ce3f6 libtool-1.5.23b.tar.gz
1bd17e86a851b1a3eca9c9e65ef26449 libtool-1.5.22-1.5.23b.diff.gz
4373d6bc39dfe49b8ef0bffa4a9aa821 libtool-1.5.22-1.5.23b.xdelta
390b679f3b40828449cbaac17c26433829bd51b6 libtool-1.5.23b.tar.gz
472c285644eae38f94c0c0d27b07dc140d66f775 libtool-1.5.22-1.5.23b.diff.gz
a717068e52a435872b03d4a41789d98e6ac31bb6 libtool-1.5.22-1.5.23b.xdelta

This prerelease should help shake out any remaining bugs for 1.5.24.
Ideally, the releases will be identical, so please test it on your
systems and with your software packages as much as you can. This
release fixes a couple of regressions on BSD systems, improves multilib
support, and treats Cygwin more like MinGW; see the NEWS excerpt below.

We intend for 1.5.24 to be the last release of the 1.5.x series.

This release was bootstrapped with Autoconf 2.61 and Automake 1.10,
but is useable with Autoconf 2.50 & later and Automake 1.4 & later
in your own projects.

Alternatively, you can fetch the unbootstrapped source code from
anonymous cvs by using the following command:

$ cvs -z3 -d :pserver:address@hidden:/sources/libtool \
co -r release-1-5-23b libtool

You will then need to have recent versions of Automake and Autoconf
installed to bootstrap the checked out sources yourself.

New in 1.5.23b: 2007-02-17

* Initial support for RDOS.
* Fix regression on DragonFly that disabled library hardcoding.
* Fix regression on OpenBSD, NetBSD, DragonFly, and other systems
with hardcode_direct=yes that wrongly removed paths to uninstalled
libraries during link mode.
* Let libltdl know that FreeBSD and DragonFly dlopen causes dependent
modules to be loaded. This fixes excessive load times for modules
with large library dependency graphs.
* Fix error with -version-info on systems with version_type=none, such
as BeOS.
* Initial support for the Sun compiler suite on GNU/Linux.
* Improved support for GNU/kFreeBSD and GNU/NetBSD.
* Search paths with GCC on multilib systems like x86_64 have been fixed.
* The libtool --tag argument which has been supported since version 1.5
is documented now.
* Fix regression in libltdl symbol exports on Cygwin. Side effect:
LT_GLOBAL_DATA and LT_SCOPE are now explicitly defined as
declspec(dllexport), bypassing auto-export logic on Cygwin.
This tracks existing behavior on MinGW.
* Bug Fixes.

Please report bugs to , 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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]