Re: LIBTOOL_OVERRIDE and ltmain.sh/libtool.m4 and gtexinfo

[Richard PALO <richard%netbsd.org@localhost>]

Le 15/03/16 09:39, Thomas Klausner a écrit :
>> Is this nevertheless the only useable approach (but using the correct directories), that is manually replacing ltmain.sh and libtool.m4
>> when libtool itself is used during the configure phase?
> 
> I haven't met another package that needs this.
> 
> Perhaps
> pre-configure: libtool-override depcomp-override
> works.
>  Thomas
> 
> 

Luckily, the simply allowing pkgsrc LIBTOOL to be used via the following seemed to work:
> diff --git a/devel/gtexinfo/patches/patch-tp_Texinfo_Convert_XSParagraph_configure b/devel/gtexinfo/patches/patch-tp_Texinfo_Convert_XSParagraph_configure
> new file mode 100644
> index 0000000..e5699d5
> --- /dev/null
> +++ b/devel/gtexinfo/patches/patch-tp_Texinfo_Convert_XSParagraph_configure
> @@ -0,0 +1,13 @@
> +$NetBSD$
> +force use of pkgsrc libtool instead of bundled to get over rm issue.
> +--- tp/Texinfo/Convert/XSParagraph/configure.orig      2016-01-30 18:04:16.000000000 +0000
> ++++ tp/Texinfo/Convert/XSParagraph/configure
> +@@ -14592,7 +14592,7 @@ esac
> + LIBTOOL_DEPS=$ltmain
> + 
> + # Always use our own libtool.
> +-LIBTOOL='$(SHELL) $(top_builddir)/libtool'
> ++#LIBTOOL='$(SHELL) $(top_builddir)/libtool'
> + 
> + 
> + 

But naturally, this requires the patch proposed to libtool/patch-ac be committed.

Jörg? 

BTW, I noticed other cases as well in ltmain.sh (libtool) of the form "... $RM <file> && ..."
which may possibly fail under the same conditions with absent files.

-- 
Richard PALO