In article <199912060453.NAA10588@dione.cec.co.jp>,
	sakamoto@cec.co.jp (Kazuki Sakamoto) writes:
> The following patch for bsd.pkg.mk reduce work of patch making for LIBTOOL.
> use USE_LIBTOOL_SYMLINK=yes instead of these patch.
> 
> 	+if false; then
> 	 # Always use our own libtool.
> 	 LIBTOOL='$(top_builddir)/libtool'
> 	...
> 	 $libtool_flags --no-verify $ac_aux_dir/ltmain.sh $host \
>	 || { echo "configure: error: libtool configure failed" 1>&2; exit 1; }
> 	+fi
> 
> pkg Makefile:
> 
> 	USE_LIBTOOL=	yes
> 	USE_LIBTOOL_SYMLINK=yes
> 	GNU_CONFIGURE=	yes
> 
> Can I commit it?

Nice idea. But it has the disadvantage that "configure" will still waste
CPU cycles with configuring and building a custom "libtool".

> +.if defined(GNU_CONFIGURE) && defined(USE_LIBTOOL) && defined(USE_LIBTOOL_SYMLINK)
> +       if [ -f ${WRKSRC}/libtool ]; then \
> +               ${RM} -f ${WRKSRC}/libtool;
> +               ${LN} -s ${LIBTOOL} ${WRKSRC}/libtool
> +       fi
> +.endif

There should be a method to specify the or more than one location of the
"libtool" binary.

	Kind regards

-- 
Matthias Scheler                            http://www.sighardstrasse.de/~tron/