Extending PATH variable in top-level Makefile
Hans Petter Selasky
hps at selasky.org
Wed Mar 11 10:20:34 UTC 2015
Hi,
When installing bmake from ports, the binary ends up in /usr/local/bin
and our top-level Makefile doesn't check there:
diff --git a/Makefile b/Makefile
index e89a5b1..35ade48 100644
--- a/Makefile
+++ b/Makefile
@@ -129,7 +129,7 @@ TGTS+= ${BITGTS}
.ORDER: buildkernel reinstallkernel
.ORDER: buildkernel reinstallkernel.debug
-PATH= /sbin:/bin:/usr/sbin:/usr/bin
+PATH= /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin
> bmake -m $PWD/share/mk buildkernel
> env: bmake: No such file or directory
> bmake: "/usr/img/freebsd/Makefile" line 136: warning: "/usr/bin/env -i PATH=/sbin:/bin:/usr/sbin:/usr/bin bmake __MAKE_CONF=/etc/make.conf -f /dev/null -V MAKEOBJDIRPREFIX dummy" returned non-zero status
> --- buildkernel ---
> --- buildkernel ---
> ERROR: Missing kernel configuration file(s) (NOIP).
> *** [buildkernel] Error code 1
>
Any objections against extending the PATH= in our top-level Makefile?
--HPS
More information about the freebsd-current
mailing list