This works around python3 having a new hash seed each time it starts to allow
a second "make" not to rebuild the world.
This should probably be reverted once we find the hash that is causing
the issue, but should reduce frustration for now.
Signed-off-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
PYTHON?=python3
WAF_BINARY=$(PYTHON) ./buildtools/bin/waf
PYTHON?=python3
WAF_BINARY=$(PYTHON) ./buildtools/bin/waf
-WAF=WAF_MAKE=1 $(WAF_BINARY)
+WAF=PYTHONHASHSEED=1 WAF_MAKE=1 $(WAF_BINARY)
PYTHON?=python3
WAF_BINARY=$(PYTHON) ../../buildtools/bin/waf
PYTHON?=python3
WAF_BINARY=$(PYTHON) ../../buildtools/bin/waf
-WAF=WAF_MAKE=1 $(WAF_BINARY)
+WAF=PYTHONHASHSEED=1 WAF_MAKE=1 $(WAF_BINARY)
PYTHON?=python3
WAF_BINARY=$(PYTHON) ../../buildtools/bin/waf
PYTHON?=python3
WAF_BINARY=$(PYTHON) ../../buildtools/bin/waf
-WAF=WAF_MAKE=1 $(WAF_BINARY)
+WAF=PYTHONHASHSEED=1 WAF_MAKE=1 $(WAF_BINARY)
PYTHON?=python3
WAF_BINARY=$(PYTHON) ../../buildtools/bin/waf
PYTHON?=python3
WAF_BINARY=$(PYTHON) ../../buildtools/bin/waf
-WAF=WAF_MAKE=1 $(WAF_BINARY)
+WAF=PYTHONHASHSEED=1 WAF_MAKE=1 $(WAF_BINARY)
PYTHON?=python3
WAF_BINARY=$(PYTHON) ../../buildtools/bin/waf
PYTHON?=python3
WAF_BINARY=$(PYTHON) ../../buildtools/bin/waf
-WAF=WAF_MAKE=1 $(WAF_BINARY)
+WAF=PYTHONHASHSEED=1 WAF_MAKE=1 $(WAF_BINARY)
# simple makefile wrapper to run waf
PYTHON?=python3
WAF_BINARY=$(PYTHON) ../../buildtools/bin/waf
# simple makefile wrapper to run waf
PYTHON?=python3
WAF_BINARY=$(PYTHON) ../../buildtools/bin/waf
-WAF=WAF_MAKE=1 $(WAF_BINARY)
+WAF=PYTHONHASHSEED=1 WAF_MAKE=1 $(WAF_BINARY)