Bug 934713 - Explicitly use $(PYTHON) to run config.status [r=gps]
authorMatt Brubeck <mbrubeck@mozilla.com>
Wed, 06 Nov 2013 13:16:44 -0800
changeset 168480 440d233acb2e
parent 168479 7dd13d06f132
child 168481 1238b4fee5b5
push id3224
push userlsblakk@mozilla.com
push dateTue, 04 Feb 2014 01:06:49 +0000
treeherdermozilla-beta@60c04d0987f1 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersgps
bugs934713
milestone28.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 934713 - Explicitly use $(PYTHON) to run config.status [r=gps] This fixes a mysterious bug where config.status has the wrong sys.path when this recipe is built using GNU Make on Windows.
Makefile.in
--- a/Makefile.in
+++ b/Makefile.in
@@ -64,17 +64,17 @@ config.status: $(topsrcdir)/configure
 # this main make file because having it in rules.mk and applied to partial tree
 # builds resulted in a world of hurt. Gory details are in bug 877308.
 #
 # The mach build driver will ensure the backend is up to date for partial tree
 # builds. This cleanly avoids most of the pain.
 
 backend.RecursiveMakeBackend:
 	@echo "Build configuration changed. Regenerating backend."
-	./config.status
+	$(PYTHON) config.status
 
 Makefile: backend.RecursiveMakeBackend
 	@$(TOUCH) $@
 
 include backend.RecursiveMakeBackend.pp
 
 default:: backend.RecursiveMakeBackend