-
Notifications
You must be signed in to change notification settings - Fork 12
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
Added support for "node-gyp" build & update deps #39
Conversation
…ion for coffee-script now
Looks like you might have missed a file? (../deps/snappy/snappy.h:45:33: error: snappy-stubs-public.h: No such file or directory). Here's the full output: What a great team effort.
|
I'm getting the exact same problem as gflarity |
My bad, it looks like |
The Chromium source holds the solution: http://src.chromium.org/svn/trunk/src/third_party/snappy/snappy.gyp They have three different directories for each of the operating systems with pregenerated I'll "borrow" their solution. ;) |
Ok, try again now! I also found out why it was working for me - I had |
both |
Two things I found
✖ 1 of 41 tests failed:
1) Iterator db.forRange() should iterate until limit key:
actual expected
107
AssertionError: "107" == ""
at i (/home/nathan/src/node-leveldb/test/iterator-test.coffee:202:18)
at exports.Iterator.Iterator.forRange.next (/home/nathan/src/node-leveldb/lib/leveldb/iterator.js:142:9)
at exports.Iterator.Iterator._wrapSeek (/home/nathan/src/node-leveldb/lib/leveldb/iterator.js:62:28) |
Good point. From what I understand 0.6.13+ should include node-gyp and should work. Travis uses Node.js 0.6.19, so the The question is do we want to use >=0.6.13 as the minimum version in package.json?
I'm running the same and I haven't seen this, awaiting your feedback! |
The tests failures happen randomly. I haven't the time to track down the issue. There's a lot of multithreading involved, that may be the issue. I haven't looked at the library in months, so it's all going over my head. Great work on the updates 👍 |
I opened a ticket for it here: #40. I think the key to debugging those issues is to record a bunch of logs from the random failures and collect them in one place. (That is assuming that @my8bird comes back confirming that this was indeed one of those random failures, of course.) |
The test error appears to be random so we can drop that from this thread since the #40 exists for that. Secondly, I pulled down v0.6.19 to test that also and it built and passed all tests. Given that I would say we update the package.json to put 0.6.13 or 19 as the minimum the library will work with so that users know what to expect. It is really cool to see all of the interest in this pull, thanks a lot all. |
Added support for "node-gyp" build & update deps
This pull request:
Tested with Node.js 0.8.3 on Ubuntu.