Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node 8 x64 binary is incompatible with GLIBC on CentOS 5.7 #13462

Closed
pmq20 opened this issue Jun 5, 2017 · 6 comments
Closed

Node 8 x64 binary is incompatible with GLIBC on CentOS 5.7 #13462

pmq20 opened this issue Jun 5, 2017 · 6 comments
Labels
build Issues and PRs related to build files or the CI.

Comments

@pmq20
Copy link
Contributor

pmq20 commented Jun 5, 2017

Node versions prior to 8 work fine, yet running Node 8 Linux x64 binary from the official download link reports the following errors.

./node: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.10' not found (required by ./node)
./node: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by ./node)
./node: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.3' not found (required by ./node)
./node: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by ./node)
./node: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by ./node)

However, I am able to compile and run Node 8 from source on my centOS 5.7 box with gcc/g++ 4.8.2.

gcc version 4.8.2 20140120 (Red Hat 4.8.2-15) (GCC) 
@pmq20 pmq20 changed the title Node 8 is incompatible with GLIBC on centOS 5.7 Node 8 x64 binary is incompatible with GLIBC on centOS 5.7 Jun 5, 2017
@pmq20 pmq20 changed the title Node 8 x64 binary is incompatible with GLIBC on centOS 5.7 Node 8 x64 binary is incompatible with GLIBC on CentOS 5.7 Jun 5, 2017
@pmq20
Copy link
Contributor Author

pmq20 commented Jun 5, 2017

Sorry this might be intentional. Just found nodejs/build#718

@gibfahn
Copy link
Member

gibfahn commented Jun 5, 2017

The minimum GLIBC and kernel versions are documented in BUILDING.md.

CentOS 5.x hasn't been supported by Node since Node 4, we've continued to build on CentOS 5 for as long as possible, but as the OS is itself EoL it's not really feasible to use it as our main build machine any more.

@gibfahn
Copy link
Member

gibfahn commented Jun 5, 2017

So yeah, it sucks for people who have CentOS 5.x systems, but at the same time if you have one of those you really should be upgrading (and if you can't you still get Node 6 support till April 2019).

@gibfahn
Copy link
Member

gibfahn commented Jun 5, 2017

@pmq20 out of interest is there a reason you haven't upgraded (I know some people can't due to unsupported hardware or because it's maintained by a company)?

@pmq20
Copy link
Contributor Author

pmq20 commented Jun 5, 2017

@gibfahn Wow thanks a lot for the detailed explanation. I am actually having case 2: it's maintained by my company.

@mscdex mscdex added build Issues and PRs related to build files or the CI. v8.x labels Jun 5, 2017
@targos
Copy link
Member

targos commented Jun 6, 2017

I guess this is answered. Please reopen if I'm wrong.

@targos targos closed this as completed Jun 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues and PRs related to build files or the CI.
Projects
None yet
Development

No branches or pull requests

4 participants