Skip to content
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

Can not install on Windows Subsystem for Linux #4

Open
jwverzijden opened this issue Jun 13, 2018 · 2 comments
Open

Can not install on Windows Subsystem for Linux #4

jwverzijden opened this issue Jun 13, 2018 · 2 comments

Comments

@jwverzijden
Copy link

Hi, I'm trying to install Scull, but it doesn't seem to compile leveldown on my system, so I checked its version and noticed this module is using an older version (^1.4.6). gist of npm install log

I'm not sure if these errors tell anything useful at all.
621: leveldown.target.mk:113: recipe for target 'Release/obj.target/leveldown/src/batch.o' failed
625: gyp ERR! stack Error: make failed with exit code: 2

I attempted to install [email protected] which installs just fine, but is not compatible as all tests just fail with spectacular errors.

information about my system:

  • windows 10 build 17134.48 using Windows Subsystem for Linux
  • node version: 10.1.0
  • npm version: 5.6.0

can the levelup and leveldown packages be updated?

@jwverzijden
Copy link
Author

jwverzijden commented Jun 13, 2018

I've tried to install on different devices, different OS.
it appears [email protected] can not compile on any system running node10.
because of:

../node_modules/nan/nan_maybe_43_inl.h:112:15: error: 'class v8::Object' has no member named 'ForceSet'
   return obj->ForceSet(isolate->GetCurrentContext(), key, value, attribs);
               ^~~~~~~~

@soletan
Copy link

soletan commented Jun 13, 2018

Ok, we should definitely add more recent versions of Node to the unit testing. Thanks for the additional information on leveldown. Nonetheless we should have a look at the dependencies. I expect you are working w/ latest release which isn't quite uptodate with our internal development progress. We are still fighting to get development ready for next release, but as with the original libskiff resilience tests are still failing too often ...

Just tell us if updating dependencies in current release would help you nonetheless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants