From fb9202d4716aeb71dcde293ff9b5d7a082cc2880 Mon Sep 17 00:00:00 2001
From: reed <reed>
Date: Thu, 2 Dec 2004 17:51:19 +0000
Subject: Make sure that the AUTOM4TE and AUTOCONF is defined in the
 environment because old (or wrong) versions may be used or the tool may be
 missing (such as not in path).

When not in path, you may receive errors like:
 sh: autom4te: not found
 aclocal-1.9: autom4te failed with exit status: 1
(noticed under Solaris)

Or if wrong versions are used, you may receive:
 autom4te: unknown language: Autoconf-without-aclocal-m4
 aclocal-1.9: autom4te failed with exit status: 1
(noticed under Mac OS X)

Maybe the correct fix would be to fix the pkgsrc-installed
aclocal and automake scripts so that the autom4te and autoconf
scripts used from within are using the correct path and version
(as also installed from pkgsrc).
---
 graphics/mng/Makefile | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'graphics')

diff --git a/graphics/mng/Makefile b/graphics/mng/Makefile
index f6d985b0029..8f1bb1d51e0 100644
--- a/graphics/mng/Makefile
+++ b/graphics/mng/Makefile
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile,v 1.19 2004/12/02 17:42:18 reed Exp $
+# $NetBSD: Makefile,v 1.20 2004/12/02 17:51:19 reed Exp $
 
 DISTNAME=	libmng-1.0.8
 PKGNAME=	${DISTNAME:S/lib//}
@@ -30,9 +30,9 @@ pre-configure:
 	cd ${WRKSRC};				\
 	${RM} -f configure.in && ${LN} -sf makefiles/configure.in .;	\
 	${RM} -f Makefile.am && ${LN} -sf makefiles/Makefile.am .;	\
-	${ACLOCAL};				\
+	${SETENV} AUTOM4TE=${LOCALBASE}/bin/autom4te ${ACLOCAL};	\
 	${LOCALBASE}/bin/libtoolize --automake;	\
-	${AUTOMAKE} -a --foreign -i;		\
+	${SETENV} AUTOCONF=${AUTOCONF} ${AUTOMAKE} -a --foreign -i;	\
 	${AUTOCONF}
 
 post-install:
-- 
cgit v1.2.3