app-text/djvu builds successfully with libtool 2.4.2-r1, but when I try to build it with libtool 2.4.3-r2, it fails with the following message: >>> Emerging (1 of 5) app-text/djvu-3.5.25.3::gentoo * djvulibre-3.5.25.3.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking djvulibre-3.5.25.3.tar.gz to /build/tmp/portage/app-text/djvu-3.5.25.3/work >>> Source unpacked in /build/tmp/portage/app-text/djvu-3.5.25.3/work >>> Preparing source in /build/tmp/portage/app-text/djvu-3.5.25.3/work/djvulibre-3.5.25 ... * Running eautoreconf in '/build/tmp/portage/app-text/djvu-3.5.25.3/work/djvulibre-3.5.25' ... * Running libtoolize --copy --force ... [ ok ] * Running aclocal -I config ... [ ok ] * Running autoconf -I config ... [ ok ] * Running autoheader -I config ... [ ok ] * Running elibtoolize in: djvulibre-3.5.25/ * Running elibtoolize in: djvulibre-3.5.25/config/ * Applying portage/1.2.0 patch ... * Applying sed/1.5.6 patch ... >>> Source prepared. >>> Configuring source in /build/tmp/portage/app-text/djvu-3.5.25.3/work/djvulibre-3.5.25 ... * econf: updating djvulibre-3.5.25/config/config.guess with /usr/share/gnuconfig/config.guess * econf: updating djvulibre-3.5.25/config/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --enable-xmltools --with-jpeg --with-tiff --disable-desktopfiles configure: error: cannot find install-sh, install.sh, or shtool in config "."/config I found out that when I try to build djvu with libtool 2.4.2-r1, it shows "libtoolize --install --copy --force", which copies install-sh, and build succeedes. But with libtool 2.4.3-r2, it shows "libtoolize --copy --force" and it does not copy install-sh, so build fails. I debugged the problem and found out that autotools.eclass strip "--install" argument if "libtoolize -n --install" fails. Indeed, "libtoolize -n --install" fails with libtool 2.4.3-r2 and runs smoothly with libtool 2.4.2-r1. For djvu to build with new libtool, I suggest to remove some more files, which will be regenerated. There is a patch to djvu ebuild: --- /build/repositories/gentoo/app-text/djvu/djvu-3.5.25.3.ebuild 2014-10-23 22:13:22.561326377 +0300 +++ /build/repositories/local/app-text/djvu/djvu-3.5.25.3.ebuild 2014-11-08 14:16:30.501733140 +0200 @@ -27,7 +27,7 @@ sed -i \ -e 's/AC_CXX_OPTIMIZE/OPTS=;AC_SUBST(OPTS)/' \ configure.ac || die #263688 - rm aclocal.m4 config/{libtool.m4,ltmain.sh,install-sh} + rm aclocal.m4 config/{libtool.m4,ltmain.sh,install-sh,config.sub,config.guess,ltoptions.m4,ltversion.m4,lt~obsolete.m4} # epatch "${FILESDIR}/${PN}-3.5.24-gcc46.patch" AT_M4DIR="config" eautoreconf } Reproducible: Always Steps to Reproduce: 1. emerge =sys-devel/libtool-2.4.3-r2; emerge app-text/djvu # build fails 2. emerge =sys-devel/libtool-2.4.2-r1; emerge app-text/djvu # build succeedes Actual Results: Build fails with new libtool. Expected Results: Build should succeed with any version of libtool.
+ 12 Nov 2014; Justin Lecher <jlec@gentoo.org> djvu-3.5.25.3.ebuild, + metadata.xml: + Add fix for newer libtool, #528638; thanks Maxim Mikityanskiy for the fix +
