-
-
Notifications
You must be signed in to change notification settings - Fork 814
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
glibc 2.14 dependency #244
Comments
You are in the right place. Thanks for the report. First off: if it's not clear: your build log above shows that node-sqlte3 installed okay in the end. It recovered from the But the The short answer is hang tight: I am working on a new release Long answer is: This error is points to a limitation of the binaries I provide for linux in that they are currently built on ubuntu precise and therefore only support systems like ubuntu precise or more modern. The standard way to support linux systems with older glibc/etc is to build binaries on an old machine. Because I'm working on automating current a future binarines on travis.ci I'm going to test a hackish approach to working around this, which I've committed in da0800b. |
Problems before this can be closed:
|
Just for the records: I am having the same issue on CentOS 6 (stuck on glibc 2.12) :( |
this happens to me with an Amazon Linux, is there any workaround I can use? |
FYI: same problem here, yes it get installed on the end but I have the "GLIBC_2.14 not found" error as well. |
Thanks for the report @wilsolutions. This is still something I need to find time to solve. |
heroku cedar stack fails too (2.11.1-0ubuntu) |
Although, if you not store node_modules in git, heroku compiled to the working state (but ugly with errors) |
Solution
|
I was getting same problem on Debian server. Then I updated the version of libc6 using following steps:
Hope this gonna help. |
It is not advised to touch libc! |
I tried many solutions but that doesn't work and then I updated the version. |
Ran into this while trying to install ghost. On debian squeeze I did:
|
Problem still exist on CentOS 6.6。Any updates? |
@yinchuan - The workarounds are:
|
Thanks! I have installed this from souce. On Mon, Mar 2, 2015 at 6:21 PM, Dane Springmeyer notifications@github.com
尹川 架构组SA |
No, no plans to change this: basically binaries are only going to work on linux as modern as Ubuntu precise because that is what Travis.ci uses, and we use Travis.ci to build binaries. I don't see this changing to support older linux that ubuntu precise - if anything we'll up the requirement more in the future. So, I'm going to close this with the recommented workaround being "npm install sqlite --build-from-source" (or if |
solved by #444, will be fixed in v3.0.6 |
Seems to be reintroduced with node-sqlite3 3.0.9? |
@adebree +1. Version 3.0.8 works for me. 3.0.9 spits this error.
|
yes, tracking fix at #484 |
I don't know for sure that i'm in the right place here. But i hope i am. My OS (Debian Wheezy) has glibc 2.13 as latest stable, see: http://packages.debian.org/wheezy/libc6
2-3 months ago i installed a node app (ghost blog) which installed fine. Now it has a dependency on 2.14 which i don't have. Is it possible to downgrade the dependency and rerun?
The relevant error message while doing npm install:
The text was updated successfully, but these errors were encountered: