[ On Monday, November 29, 2004 at 16:22:57 (-0800), Jeremy C. Reed wrote: ]
> Subject: graphics/mng and PATH for autom4te and autoconf
>
> It seems like having the ${LOCALBASE}/bin as part of the default path
> should not be required. That is why it is set in MAKE_ENV and
> CONFIGURE_ENV for example.

Indeed.

I've been using something much like the following change for a very long
time now and except for a few strange places where HOME is needed by
something that shouldn't need it (python, for example), I've had good
success.

Index: mk/defs.NetBSD.mk
===================================================================
RCS file: /cvs/master/m-NetBSD/main/pkgsrc/mk/Attic/defs.NetBSD.mk,v
retrieving revision 1.69
diff -u -r1.69 defs.NetBSD.mk
--- mk/defs.NetBSD.mk	27 Aug 2004 06:29:09 -0000	1.69
+++ mk/defs.NetBSD.mk	10 Sep 2004 18:25:55 -0000
@@ -59,11 +57,16 @@
 RMDIR?=		/bin/rmdir
 RSH?=		/usr/bin/rsh
 SED?=		/usr/bin/sed
-SETENV?=	/usr/bin/env
+SETENV?=	/usr/bin/env -i
 SH?=		/bin/sh
 SHLOCK=		/usr/bin/shlock
 SORT?=		/usr/bin/sort



I would _strongly_ recommend that "env -i" _always_ be used....

(as it should be used by any decent build system -- the builder's login
shell environment should _never_ be used)


> But I was building graphics/mng and it failed first with missing autom4te

However I don't think I've ever installed graphics/mng....  :-)

-- 
						Greg A. Woods

+1 416 218-0098                  VE3TCP            RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>          Secrets of the Weird <woods@weird.com>