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

Supported node versions should be specified #19

Closed
cluebcke opened this issue Feb 6, 2015 · 4 comments
Closed

Supported node versions should be specified #19

cluebcke opened this issue Feb 6, 2015 · 4 comments

Comments

@cluebcke
Copy link
Contributor

cluebcke commented Feb 6, 2015

I had forgotten I had iojs-v1.1.0 installed--build failed. So I switched back to the latest stable node, v0.10.36. The build succeeded but when I ran node mozaik.js, I received the following error:

$ node mozaik.js
dyld: lazy symbol binding failed: Symbol not found: _node_module_register
  Referenced from: /Users/cluebcke/projects/tools/mozaik/node_modules/ws/build/Release/bufferutil.node
  Expected in: dynamic lookup

dyld: Symbol not found: _node_module_register
  Referenced from: /Users/cluebcke/projects/tools/mozaik/node_modules/ws/build/Release/bufferutil.node
  Expected in: dynamic lookup

Trace/BPT trap: 5

So I switched to v0.11.16 (yay nvm!) and now everything is fine.

@plouc
Copy link
Owner

plouc commented Feb 6, 2015

@cluebcke did you ran npm install on iojs-v1.1.0 then switched to v0.10.36 ?

@cluebcke
Copy link
Contributor Author

cluebcke commented Feb 6, 2015

Actually yeah I did. Quite admittedly not the cleanest process, so I couldn't say exactly what combination of things made it all not work.

@cluebcke
Copy link
Contributor Author

cluebcke commented Feb 6, 2015

So I just switched to node v0.10.36 and re-cloned/installed/published in a fresh branch. Everything was fine. So that must have been caused by me bouncing around node versions between install and publish, which is nobody's idea of a supported use case. Sorry for the fuss, and thanks for being so responsive.

@plouc
Copy link
Owner

plouc commented Feb 7, 2015

Probably caused by ws package, I've seen some issues regarding node-gyp/native addons, especially on OSX. I tried to run my tests on travis with node 0.11.* and iojs, but the build failed due to package install, it's good to know the limitations, thanks for reporting your problems.

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