Replies: 1 comment
-
There isn’t a specific --flag to force glibc in Node.js’s configure script. The solution is to adjust your environment variables and paths so that the build process picks up glibc’s libraries and toolchain rather than those provided by musl. This typically involves setting your CC, CXX, and LDFLAGS appropriately and ensuring that your LD_LIBRARY_PATH points to glibc directories. I personally feels to avoid the mess you can test using a container image (e.g., an official Ubuntu image) that doesn’t have musl installed. This way you can be sure that glibc is the only libc available. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
i try to build nodejs in github action and fork the nodejs github and then
`./configure
make`
now i always get
/home/runner/work/node/node/out/Release/node_js2c: error while loading shared libraries: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory
how to build nodejs just with glibc? which flag i shoud pass to configure? i have apt install musl package in system for some other purpose. but i do not want to build nodejs against musl. just use glibc. please help.
Beta Was this translation helpful? Give feedback.
All reactions