STEPS TO REPRODUCE 1. clone mozilla-inbound 2. save the attached mozconfig in the working directory 3. mkdir OBJDIR 4. python build/pymake/make.py -f client.mk ACTUAL RESULT see attached build log This is a regression in the past week or so.
Yeah, we're trying to use pymake native commands but prefixing the entire thing with PYTHONDONTWRITEBYTECODE=1 which causes pymake to not use native commands. This is a result of bug 741125 (Update WebIDL parser, khuey). But that's not the proximate cause of this; perhaps we started using more pymake native commands in the past week? I can't imagine that replacing PYTHON with % would work in many cases given how we sometimes use it in shell contexts...
bz switched a bunch of stuff in this directory to use $(PYTHONPATH) instead of $(PYTHON) config/... last week. Perhaps we should revert that?
FWIW, the naive workaround here that worked for me is running GNU Make inside 'dom' when I hit that error (which fails pretty quickly if the rest of your objdir isn't up to date). And then running pymake again.
WIN7 responds to GNU make with ../config/autoconf.mk:705: *** Windows-style srcdir being used with GNU make. Did you mean to run c:/Users/Master/mozilla-central/build/pymake/make.py instead? [see-also: https://developer.mozilla.org/en/Gmake_vs._Pymake]. Stop. No help for the evil ...
Whatever it was it seems to be fixed now - a clean build from the tip of mozilla-inbound works fine for me.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
Oh, I landed a fix. http://hg.mozilla.org/mozilla-central/rev/b3e69a65a7b7 Just forgot to mark the bug.
Resolution: WORKSFORME → FIXED
Assignee: nobody → khuey
You need to log in before you can comment on or make changes to this bug.