Libtool-2.2.6a

[Jeremy Huntwork]

New version, see: ​http://lists.gnu.org/archive/html/autotools-announce/2008-04/msg00000.html

[Julio Meca Hansen]

I'd be cautious with this package, seems there's some perceptible differences between this version and 1.5.26, at least for me, I couldn't compile some packages in the BLFS/CBLFS book due to some errors.

I would like to write down that errors to give an example, but wiped out that system as it turned out to be quite unusable so rebuilt another and I don't have the logs, but anyone willing could take the same test and get the same results.

Anyway, that's my advice... don't touch this package... not yet, at least

Julio

[Julio Meca Hansen]

New version (2.2.4), released as of May 4th of 2008

​ftp://ftp.gnu.org/pub/gnu/libtool/libtool-2.2.4.tar.bz2 ​ftp://ftp.gnu.org/pub/gnu/libtool/libtool-2.2.4.tar.gz

Anyway, my advice keeps being quite safe, this package is not ready for prime time in LFS, and I've done some testing of both 2.2.2 and 2.2.4, both with negative results.

The 'most' important package if fails with is... Linux-PAM, so from my point of view, it has no sense on trying to continue any kind of testing if one of the most important packages (security-wise) in a Linux system can't compile due to this new version, so my recommendation is to continue using version 1.5.26

Julio

[randy@…]

I'm confident that the 2.2.6 version brings on no issues in LFS (can't speak for all of BLFS, however). I'm going to go with the update.

Note that the maintainer made a small goof in .so naming so he released a 2.2.6a tarball that is identical to the 2.2.6 tarball other than the small .so name change. There is information in Ticket #2205 about this along with a URL to the maintainers description of the release.

[randy@…]

Closing this ticket as the book was updated to the 2.2.6 version and it seems there is very few issues with BLFS and Beyond packages. I read over a mailing list topic over at DIY where Dan Nicholson says there was only one package (I can't recall what it was) that wasn't working and that more and more packages are being updated to work with this version of Libtool.