Cannot compile node
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Cannot compile node 13.0.1 with flags ./configure --fully-static --with-intl=full-icu inside docker image for node
Getting this output
LD_LIBRARY_PATH=/node/out/Release/lib.host:/node/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../tools/v8_gypfiles; mkdir -p /node/out/Release/obj/gen/src/regexp; python ../../deps/v8/tools/run.py "/node/out/Release/gen-regexp-special-case" "/node/out/Release/obj/gen/src/regexp/special-case.cc"
tools/v8_gypfiles/run_gen-regexp-special-case.target.mk:13: recipe for target '/node/out/Release/obj/gen/src/regexp/special-case.cc' failed
make[1]: *** [/node/out/Release/obj/gen/src/regexp/special-case.cc] Error 245
make[1]: *** Waiting for unfinished jobs....
rm 889aa6e08bf291915b2edfb5755eacba271e7d14.intermediate
Makefile:101: recipe for target 'node' failed
make: *** [node] Error 2
Steps to reproduce:
- Install docker
docker run -it node bash
//inside docker shellgit clone https://github.com/nodejs/node.gitcd nodegit checkout v13.0.1./configure --fully-static --with-intl=full-icumake -j8
Also not working with flags ./configure --fully-static --enable-static --with-intl=full-icu with the same error
But it compiles without errors with version 11.1.0 with flags ./configure --fully-static --with-intl=full-icu --download=all
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure in the node Docker image by checking out v13.0.1, running ./configure --fully-static --with-intl=full-icu, and then make -j8. Start with the tools/v8_gypfiles/run_gen-regexp-special-case.target.mk failure and compare the v13.0.1 build with v11.1.0. Done means the reported v13.0.1 configuration compiles successfully or the issue is narrowed to a documented prerequisite or build failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript, node.js
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100