-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
last versions of node for linuxppc64 requires glib >= 2.15 but maximal version on this platform is 2.11 #28186
Comments
/cc @nodejs/platform-ppc |
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? |
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. |
@sam-github, 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. |
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. |
Yes, I'm currently trying to build from source. I'll keep you informed in this matter. |
FYI: #12309 (comment) |
@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? |
@mhdawson I wish I can answer that, it's driven from our clients needs for what I know. |
@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? |
@mhdawson Yes it is. I did manage to build the application. I think I'll go this way, thanks ! |
node: /lib64/power7/libc.so.6: version `GLIBC_2.15' not found (required by node)
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
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:
Every version of node requires glibc >= 2.15 (see error in output of
node -v
)This requirement for the binary is impossible to have without compromising the platform.
The text was updated successfully, but these errors were encountered: