summaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorjmmv <jmmv@FreeBSD.org>2014-07-13 23:53:41 +0000
committerjmmv <jmmv@FreeBSD.org>2014-07-13 23:53:41 +0000
commit0b964c341a8548648d88f3097969b1e9b707da2e (patch)
tree0fc1c163e853ad91c49c4452890b1e5ce8fe5e16 /Makefile
parent4f68aa7fc4fade24671e02ec2a17a5d1475fe386 (diff)
downloadFreeBSD-src-0b964c341a8548648d88f3097969b1e9b707da2e.zip
FreeBSD-src-0b964c341a8548648d88f3097969b1e9b707da2e.tar.gz
Explicitly disable the build of tests when building bmake.
During "make buildworld", building bmake is (one of) the very first steps and we should not be building any of its tests. Conceptually, this is the right thing to do 1) for build simplicity reasons and 2) because there is no need to build any tests this early on. In practice, this fixes tinderbox builds of CURRENT from 9.x when MK_TESTS is enabled. This is because bsd.test.mk needs some modern bmake features not present in 9.x (:tW) and tinderbox is forcing the build to use the CURRENT share/mk files from the very beginning (see r266617). By skipping the build of the tests when still using the host make, we omit the problem. Arguably, what tinderbox is doing is wrong and needs to be addressed, but that is a separate issue.
Diffstat (limited to 'Makefile')
-rw-r--r--Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/Makefile b/Makefile
index d0c2402..074be67 100644
--- a/Makefile
+++ b/Makefile
@@ -331,6 +331,7 @@ MMAKEENV= MAKEOBJDIRPREFIX=${MYMAKE:H} \
MMAKE= ${MMAKEENV} ${MAKE} \
-DNO_MAN -DNO_SHARED \
-DNO_CPU_CFLAGS -DNO_WERROR \
+ MK_TESTS=no \
DESTDIR= PROGNAME=${MYMAKE:T}
bmake: .PHONY
OpenPOWER on IntegriCloud