Repository navigation
last versions of node for linuxppc64 requires glib >= 2.15 but maximal version on this platform is 2.11 #28186
Description
- Version:
node: /lib64/power7/libc.so.6: version `GLIBC_2.15' not found (required by node) - Platform:
Linux lsh35056 3.0.101-0.42.1.7881.0.PTF-default deps: update openssl to 1.0.1j #1 SMP Tue Jan 20 12:53:10 UTC 2015 () ppc64 ppc64 ppc64 GNU/Linux - Subsystem:
N/A
Linuxppc64 is running on SLES11 SP3 on which the latest glibc version available is 2.11
Even runnning on SLES11 SP4 glibc is still in version 2.11.
I've tested several version of NodeJS binaries on linuxppc64 so far:
- 8.9.1
- 8.2.1
- 6.12.3
- 6.12.0
Every version of node requires glibc >= 2.15 (see error in output ofnode -v)
This requirement for the binary is impossible to have without compromising the platform.
Activity
BethGriggs commentedon Jun 12, 2019
/cc @nodejs/platform-ppc
sam-github commentedon Jun 12, 2019
Can you clarify something: you say "latest versions of node need glibc>=2.15" in the report title, but then in the body you list a bunch of very old (not latest) versions of node, and say they also require glibc >=2.15, so, doesn't that mean nothing has changed?
mhdawson commentedon Jun 12, 2019
As far back as 6.x and before (see https://github.com/nodejs/node/blob/v6.x/BUILDING.md) it's been documented that the glibc level is 2.19 or higher for the binaries built by the community.
Ghrisly commentedon Jun 13, 2019
@sam-github,
"latest versions of node for linuxppc64 need glibc >= 2.15" (I should have been more precise)
Seems that linuxppc64 support has ended with version 8.9.2
What @mhdawson states is what I understood, but I don't understand how to build on linuxppc64 with a higher glibc when the platform's version stops at 2.11 on SLES11...
Maybe there is no answer.
I'll try to brutally use a higher glibc to build node on linuxppc64, but it shouldn't be this way :'(
sam-github commentedon Jun 13, 2019
SLES11 was released 10 years ago and probably has its glibc version unchanged since then. Also, SLES11 is itself no longer supported, if I read SUSE's site correctly. There are practical difficulties in building portable binaries that run on such ancient systems.
Just because our binaries require a certain glibc version doesn't mean that version is required if you recompile from source. Have you tried building from source? If it doesn't build, please get back to us with the issues, it may be that small changes we make would help you build.
Ghrisly commentedon Jun 13, 2019
Yes, I'm currently trying to build from source. I'll keep you informed in this matter.
sam-github commentedon Jun 13, 2019
FYI: #12309 (comment)
mhdawson commentedon Jun 13, 2019
@Ghrisly I am interested in the need for SLES11 in this case. Is it a migration from another platform or something else that is driving the need for SLES11 versus something newer?
Ghrisly commentedon Jun 14, 2019
@mhdawson I wish I can answer that, it's driven from our clients needs for what I know.
I already asked if we could update but it would impact too many projects on this platform.
mhdawson commentedon Jun 17, 2019
@Ghrisly ok, building from source is probably your best bet. I assume that this is a "new" application you want to add to an existing machine as the community binaries would never have run on SLES11, right?
Ghrisly commentedon Jun 18, 2019
@mhdawson Yes it is. I did manage to build the application. I think I'll go this way, thanks !