Closed
Bug 879809
Opened 11 years ago
Closed 11 years ago
MOZBUILD_BACKEND_CHECKED should be unset when processing external directories
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla24
People
(Reporter: RyanVM, Assigned: gps)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
6.43 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
This push removed a file and deleted its corresponding moz.build entry. However, the build slaves were still looking for it.
https://hg.mozilla.org/integration/mozilla-inbound/rev/25ea966531ca
https://tbpl.mozilla.org/php/getParsedLog.php?id=23814634&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=23815235&tree=Mozilla-Inbound
Assignee | ||
Comment 1•11 years ago
|
||
It appears config.status didn't run for js/src despite a moz.build file changing. Most interesting.
Assignee | ||
Comment 2•11 years ago
|
||
The problem is that MOZBUILD_BACKEND_CHECKED (a global flag used to determine whether moz.build rebuild scan and possibly rebuild has been performed) is defined by the root Makefile and exported to the environment under which js/src executes. js/src should get a "fresh" environment not polluted with this variable.
Assignee: nobody → gps
Status: NEW → ASSIGNED
Summary: Bug 875929 required a clobber → MOZBUILD_BACKEND_CHECKED should be unset when processing external directories
Assignee | ||
Comment 3•11 years ago
|
||
This should do it. I wish this could be done with make syntax instead of
shell. However, SUBMAKE gets $(call)ed inside a recipe and thus its
output is evaluated as shell commands, not make. It's ugly.
Attachment #761737 -
Flags: review?(ted)
Comment 4•11 years ago
|
||
Comment on attachment 761737 [details] [diff] [review]
Don't export MOZBUILD_BACKEND_CHECKED to independent build systems
Review of attachment 761737 [details] [diff] [review]:
-----------------------------------------------------------------
::: config/rules.mk
@@ +428,3 @@
> +@$(UPDATE_TITLE)
> ++@if test -n "$(3)"; then \
> + MOZBUILD_BACKEND_CHECKED= $(MAKE) $(if $(2),-C $(2)) $(1); \
So, you could write this as another make $(if), right?
+$(if $(3) MOZBUILD_BACKEND_CHECKED= ) $(MAKE) $(if $(2),-C $(2)) $(1)
Comment 5•11 years ago
|
||
Comment on attachment 761737 [details] [diff] [review]
Don't export MOZBUILD_BACKEND_CHECKED to independent build systems
Review of attachment 761737 [details] [diff] [review]:
-----------------------------------------------------------------
Clearing review till you consider my proposal.
Attachment #761737 -
Flags: review?(ted)
Assignee | ||
Comment 6•11 years ago
|
||
Switched to inline $(if) (I keep forgetting this exists).
Assignee | ||
Updated•11 years ago
|
Attachment #761737 -
Attachment is obsolete: true
This needs to be fixed immediately.
Severity: major → blocker
Comment 8•11 years ago
|
||
Comment on attachment 763691 [details] [diff] [review]
Don't export MOZBUILD_BACKEND_CHECKED to independent build systems
Review of attachment 763691 [details] [diff] [review]:
-----------------------------------------------------------------
r=me if this doesn't break pymake.
Attachment #763691 -
Flags: review+
Assignee | ||
Comment 9•11 years ago
|
||
Comment 10•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla24
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•