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

Runtime errors on Mac OSX #133

Open
alflanagan opened this issue Jan 28, 2020 · 4 comments
Open

Runtime errors on Mac OSX #133

alflanagan opened this issue Jan 28, 2020 · 4 comments

Comments

@alflanagan
Copy link

alflanagan commented Jan 28, 2020

After installing version 1.34.0, I'm getting two error messages trying to run vmd. Version 1.33.0 worked fine, and after re-installing it worked normally again. Also, installing into the nvm environment for node 13.5.0 also worked.

$ nvm --version
0.35.1
$ npm --version
6.13.6
$ node --version
v10.18.1
$ vmd --version
1.34.0
$ uname -a
Darwin ******-MacBook-Pro.local 19.2.0 Darwin Kernel Version 19.2.0: Sat Nov  9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 x86_64

nvm was installed with Homebrew.

The errors received are:

$ vmd
dyld: lazy symbol binding failed: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/adrianflanagan/.nvm/versions/node/v10.18.1/lib/node_modules/vmd/node_modules/fsevents/build/Release/fse.node
  Expected in: flat namespace

dyld: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/adrianflanagan/.nvm/versions/node/v10.18.1/lib/node_modules/vmd/node_modules/fsevents/build/Release/fse.node
  Expected in: flat namespace
@mikemimik
Copy link

mikemimik commented Feb 12, 2020

Doing some prelim investigations and it appears that node@10 is an issue. My hunch is that it has something to do with node-gyp.

@alflanagan if you reinstall vmd in lts/erbium (node@12), it will work.


Investigation

  • .travis.yml only tests node@7 and node@lts: This issue would probably have been caught if the matrix was all LTS version of node.

@xavierchow
Copy link

I have the same issue on node v10.14.1

@rwanyoike
Copy link

rwanyoike commented Apr 5, 2020

@mprokopov
Copy link

works with node v12, but doesn't work with node v10

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

5 participants