Repository navigation
Makefile dependency tree is incomplete, makefiles do not build only as necessary #25135
Description
- Version: master
- Platform:Linux samtu 4.18.0-12-generic Failed assert in AsyncWrap::MakeCallback(uint32_t, int, Handle) from test-timers-unref.js on ARM #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
- Subsystem: gyp/make
The makefiles generated by gyp are not working for development (they work better for single-shot CI builds). Perhaps I'm missing something, please tell me if I am, but I've done some asking around to people who know the gyp system, and have some agreement on these points.
-
make node; make nodeMake should do nothing if no source code has been changed, butmake noderelinks bothnodeandcctest(!?) every time it is run. -
make -C out nodeis faster,butand builds just node, not cctest, but it does it even if no source has changed. However, its build/dependency tree is incomplete! It doesn't run js2c so if any js source files are changed they will not be built-in with js2c. Fast and wrong is worse than slow. -
make -C out/Release nodeas above -
make -j4 node; make -j1 testoften required. parallel make is not working for test. Various symptoms of brokenness occur (irc has some discussion). Sounds like this could be related to the dependency relationships not being correctly specified, causing build rules to run in parallel when they cannot, and thus be racy. -
./configure --shared-openssl-includeswill cause openssl include paths to be passed to dependencies that don't use openssl. This might appear harmless, but it (for example) causes ccache to rebuild icu, even though icu doesn't use openssl. Possible fix:, addLines 549 to 560 in eef6504
['node_shared_openssl!="true"', { # `OPENSSL_THREADS` is defined via GYP for openSSL for all architectures. 'defines': [ 'OPENSSL_THREADS', ], }], ['node_shared_openssl!="true" and openssl_no_asm==1', { 'defines': [ 'OPENSSL_NO_ASM', ], }], ], OPENSSL_THREADSto the else clause (I haven't tried yet).
Ninja notes:
Ninja (./configure --ninja) doesn't have the above problems for building, its dependency tree is correct (it builds nothing when nothing has changed, and it reruns js2c when js files have changed).
However, it is either incomplete or not integrated with the rest of the build (I'm not sure how its intended to work). It doesn't make the top-level node symlink (at least test-doc relies on this), so a ln -s out/Release/node node is required for make test-doc. As for make test, it won't use the ninja build output, because it relies on .PHONY targets, so it always (effectively) does a make -C out all.
Activity
sam-github commentedon Dec 20, 2018
An additional issue:
sam-github commentedon Dec 28, 2018
sam-github commentedon Nov 28, 2019
This is pretty painful on machines with slow link times while testing CI builds (so, not allowed to use ninja), because
make testdoes a relink every time.I have been poking at this a bit, and it appears to be a bug in the V8 gyp files (@nodejs/v8-update), they seem to do some actions without considering whether deps have changed. Following is a rebuild (after just having done 5 clean builds). Is the root cause of this that
Generating inspector protocol sources from protocol jsonhas no deps?jasnell commentedon Jan 22, 2025
There's been no further discussion or activity here in many years. Is this still relevant or can we go ahead and close this?