GNU bug report logs - #18910
GNU Libtool-2.4.3 released [stable]

Previous Next

Full log

View this message in rfc822 format

From: Pavel Raiskup <praiskup <at> redhat.com>
To: libtool <at> gnu.org, 18910 <at> debbugs.gnu.org
Subject: bug#18910: GNU Libtool-2.4.3 released [stable]
Date: Thu, 30 Oct 2014 14:06:05 +0100

[Message part 1 (text/plain, inline)]

Thanks for the release, Gary and all!

On Monday 27 of October 2014 21:44:02 Gary V. Vaughan wrote:
>  - 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.

It is not completely the same situation like with automake, but
gnulib-origin files are causing similar problems [1].

Taking into account the package relies on some gnulib files in question
itself (not via libtool), the package should still be easily autoreconfed
from distributed tarballs with (relatively) safe command
'autoreconf -vfi'.

However now (a) libtoolize removes gnulib files and (b) build machine (or
the user) may have no idea what gnulib is when working with 'make dist'ed
tarball.  If there is no reason for current libtoolize to install those
files, the patch attached could help.  That is not a solution for
"upgrade" cleanup but can there be other safe solution?

Also, I'm not sure what to do with 'argz.m4'.  That file can be updated by
package maintainer via gnulib-tool, however libtool (via autoreconf -vfi
e.g.) can overwrite it with older version of this file.  That however does
not break the build, at least not now.

[1] https://bugs.gentoo.org/show_bug.cgi?id=527200

Pavel

[0001-libtoolize-do-not-remove-gnulib-files-with-force.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.