-
-
Notifications
You must be signed in to change notification settings - Fork 832
Installation with npm fails, again... #27
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
Comments
What version of the sqlite3 library do you have installed? If in doubt, you should update yours to a more recent 3.7.x version. |
I was running 3.5.x (from an apt-get install sqlite3). I installed the latest version of sqlite3 from source, which now throws runtime errors when I attempt to start the program. However, node-sqlite3 installs fine now so we'll see how that goes... Thanks for your help, much appreciated. |
I have SQLite version 3.7.4 and I'm getting also this:
|
Trying to build, but I get this:
I do have these installed:
Also, I don't seem to have sqlite3.pc file anywhere (Ubuntu 11.04). Thanks. |
Never mind, I didn't have libsqlite3-dev installed. Sorry about this. |
Although, maybe, if that package could be checked on the installation phase, those who don't read instructions could get around it :) |
I have resolved runtime errors by downgrading to sqlite 3.7.3 and node-sqlite3 is now working as expected. Thanks again for the support. |
@djroshi, what version were you using before? |
Version 3.5.9-6. All working now, running 3.7.3-1. |
Ah sorry, I only tested it with 3.6+. I'll add a version information to the README. |
That was surprisingly challenging. |
Nothing to clean (project not configured)
Setting srcdir to : /root/node_modules/sqlite3
Setting blddir to : /root/node_modules/sqlite3/build
Checking for program g++ or c++ : /usr/bin/g++
Checking for program cpp : /usr/bin/cpp
Checking for program ar : /usr/bin/ar
Checking for program ranlib : /usr/bin/ranlib
Checking for g++ : ok
Checking for node path : not found
Checking for node prefix : ok /root/local/node
Checking for program pkg-config : /usr/bin/pkg-config
Checking for sqlite3 : yes
'configure' finished successfully (0.055s)
Waf: Entering directory
/root/node_modules/sqlite3/build' [1/4] cxx: src/sqlite3.cc -> build/default/src/sqlite3_1.o [2/4] cxx: src/database.cc -> build/default/src/database_1.o ../src/database.cc: In static member function 'static v8::Handle<v8::Value> node_sqlite3::Database::New(const v8::Arguments&)': ../src/database.cc:134: error: 'SQLITE_OPEN_FULLMUTEX' was not declared in this scope Waf: Leaving directory
/root/node_modules/sqlite3/build'Build failed: -> task failed (err #1):
{task: cxx database.cc -> database_1.o}
npm ERR! error installing sqlite3@2.0.13 Error: sqlite3@2.0.13 preinstall:
node-waf clean || true; node-waf configure build
npm ERR! error installing sqlite3@2.0.13
sh "-c" "node-waf clean || true; node-waf configure build"
failed with 1npm ERR! error installing sqlite3@2.0.13 at ChildProcess. (/root/local/node/lib/node_modules/npm/lib/utils/exec.js:49:20)
npm ERR! error installing sqlite3@2.0.13 at ChildProcess.emit (events.js:67:17)
npm ERR! error installing sqlite3@2.0.13 at ChildProcess.onexit (child_process.js:192:12)
npm ERR! sqlite3@2.0.13 preinstall:
node-waf clean || true; node-waf configure build
npm ERR!
sh "-c" "node-waf clean || true; node-waf configure build"
failed with 1npm ERR!
npm ERR! Failed at the sqlite3@2.0.13 preinstall script.
npm ERR! This is most likely a problem with the sqlite3 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-waf clean || true; node-waf configure build
npm ERR! You can get their info via:
npm ERR! npm owner ls sqlite3
npm ERR! There is likely additional logging output above.
npm ERR!
npm ERR! System Linux 2.6.26-2-amd64
npm ERR! command "node" "/root/local/node/bin/npm" "install" "sqlite3"
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /root/npm-debug.log
npm not ok
I have tried the audriusk@d19cfaf changeset also (previous thread #25) but same message...
The text was updated successfully, but these errors were encountered: