Closed Bug 1006275 Opened 10 years ago Closed 9 months ago

Spidermonkey31 build fails due to missing .deps/binaries.pp with make -j > 1

Categories

(Core :: JavaScript Engine, defect)

31 Branch
x86_64
Linux
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: darkxst, Unassigned)

Details

Currently standalone Spidermonkey 31 build fails due to missing binaries.pp

This file is in
js/src/.deps/binaries.pp

However the build scripts seem to be looking for it in
js/src/js/src/.deps/binaries.pp


../../dist/bin/nsinstall -R -m 644 'libmozjs-31a2.so' '../../dist/bin'
../../dist/bin/nsinstall -R -m 644 'libmozjs-31a2.so' '../../dist/lib'
../../dist/bin/nsinstall -R -m 644 'libmozjs-31a2.so' '../../dist/sdk/lib'
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/media/gstore/src/jhbuild-checkout/source/js31-31.0.2/python/mozbuild/mozbuild/action/link_deps.py", line 229, in <module>
    main(sys.argv[1:])
  File "/media/gstore/src/jhbuild-checkout/source/js31-31.0.2/python/mozbuild/mozbuild/action/link_deps.py", line 219, in main
    linker.add_dependencies(open(f))
IOError: [Errno 2] No such file or directory: '.deps/binaries.pp'
/media/gstore/src/jhbuild-checkout/source/js31-31.0.2/config/recurse.mk:208: recipe for target 'libs' failed
make[3]: *** [libs] Error 1
make[3]: Leaving directory '/media/gstore/src/jhbuild-checkout/source/js31-31.0.2/js/src/js/src'
/media/gstore/src/jhbuild-checkout/source/js31-31.0.2/config/recurse.mk:95: recipe for target 'js/src/libs' failed
make[2]: *** [js/src/libs] Error 2
make[2]: Leaving directory '/media/gstore/src/jhbuild-checkout/source/js31-31.0.2/js/src'
/media/gstore/src/jhbuild-checkout/source/js31-31.0.2/config/recurse.mk:39: recipe for target 'libs' failed
make[1]: *** [libs] Error 2
make[1]: Leaving directory '/media/gstore/src/jhbuild-checkout/source/js31-31.0.2/js/src'
/media/gstore/src/jhbuild-checkout/source/js31-31.0.2/config/rules.mk:592: recipe for target 'default' failed
Builds work if you do an out-of-source build.  I *was* able to make an in-source build work, once, yesterday; but I cannot reproduce that today (no matter how many different configurations I try).
Flags: needinfo?(mh+mozilla)
(In reply to darkxst from comment #0)
> This file is in
> js/src/.deps/binaries.pp
> 
> However the build scripts seem to be looking for it in
> js/src/js/src/.deps/binaries.pp


For the (one) build attempt I had that worked, there was a .deps/binaries.pp in both js/src and js/src/js/src ...
I can't reproduce.
Flags: needinfo?(mh+mozilla)
Per suggestion of glandoim on IRC last night, I tried this on m-c (checkout as of 10am EDT)..

If using parallel make (ie, "make -j6" is my usual), it fails the same way, however it will succeed with a "make -j1".


(i'll only back-handedly comment about how a build system update that's supposed to improve compilation times removes the ability to successfully build in parallel :P )

Updating bug description.  darkxst, could you confirm what MAKEOPTS you're using?  are you building parallel too?
Summary: Spidermonkey31 build fails due to missing .deps/binaries.pp → Spidermonkey31 build fails due to missing .deps/binaries.pp with make -j > 1
I am using the default jhbuild environment, which I believe sets -j to the number of available cores, so probably -j4 in my case.

Forcing -j1 does fix the build failures.
So with 1007788 in the process of being landed, do we just want to backport that to aurora and treat this bug as closed?
Flags: needinfo?(mh+mozilla)
Seems reasonable to close, parallel builds out-of-source work fine here.
actually no, building a clean out-of-source tree still fails when doing parallel build.
moreinfo already provided so dropping the flag.  But codebases and build systems have evolved so far beyond this now the bug can likely be ignored.
Flags: needinfo?(mh+mozilla)
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.