-
Notifications
You must be signed in to change notification settings - Fork 31
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
Warning: /lib64/libc.so.6: version `GLIBC_2.14' not found #44
Comments
Sorry about that! I did change the alpha builds (never 1.6.x) four times to get broader binary compatibility. I added an "official" glibc version to target in 59f8822. It's a mystery to me how it ever worked for you since before I was building on Ubuntu 12.04, which has glibc 2.14. Maybe at one point I was using a really old distro for the docker image Anyways, your version of glibc is from 2010 and most distros that have glibc that old are not supported anymore 😕. I don't want to have to compile glibc from source so right now I can only support 2.13 and up since it comes with Debian Wheezy. |
That's sad 😞 Thanks for the answer. |
Sorry about that. If I find the time maybe I can try building on a CentOS docker image instead of Debian, since it seems to have the oldest libc. |
I'll try it too. Also, please publish git repository of |
Cool, it's right here. Once you get the build deps, hopefully all the commands beyond that Just Work. |
At my company we are using
node-canvas-prebuilt@~2.0.0-alpha.2
to build PNG sprite images. Everything works fine.Suddenly, on some machines,
yarn
is reinstallingnode-canvas-prebuilt
even when dependencies remain unchanged. Don't know why - it's another question.yarn
downloads canvas-prebuilt-v2.0.0-alpha.2-node-v57-linux-x64. This is a correct behavior. But after installation build script is failing with error.I made a backup of correct
canvas.node
and we are replacing wrong one when issue occurs. After replacement everything works as usual without errors.Re-installation of
node_modules
andyarn cache clean
doesn't help.It seems like
canvas.node
in that tarball was changed after release. At instance, file size differs from the previous one. I don't know if that possible, but this is my only assumption.Versions of
Node
,npm
andyarn
are the same on every development machine.Node.js version:
v8.11.2
yarn version:
1.3.2
npm version:
5.6.0
OS and libc versions are the same too: CentOS 6.9 and GNU libc v2.12.
To summarize, I have two questions:
canvas.node
was changed in archive file of June 2017 release?yarn
to not to re-install installed binary (probably, this question should be asked somewhere else).The text was updated successfully, but these errors were encountered: