Skip to content

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

Closed

Description

@pmq20

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) 

Activity

  1. 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[/+] on Jun 5, 2017
  2. 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[/+] on Jun 5, 2017
  3. pmq20 commented on Jun 5, 2017

    @pmq20
    ContributorAuthor

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

  4. gibfahn commented on Jun 5, 2017

    @gibfahn
    Member

    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.

  5. gibfahn commented on Jun 5, 2017

    @gibfahn
    Member

    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).

  6. gibfahn commented on Jun 5, 2017

    @gibfahn
    Member

    @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)?

  7. pmq20 commented on Jun 5, 2017

    @pmq20
    ContributorAuthor

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

  8. added
    buildIssues and PRs related to Node.js builds or CI infrastructure.
    on Jun 5, 2017
  9. targos commented on Jun 6, 2017

    @targos
    Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildIssues and PRs related to Node.js builds or CI infrastructure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions