LinusU / node-appdmg

💾 Generate your app dmgs
MIT License
1.68k stars 152 forks source link

dyld: lazy symbol binding failed: Symbol not found #167

Closed markmorris closed 5 years ago

markmorris commented 5 years ago

Hope you can point me in the right direction. This only happens when i try and set an Icon when creating a DMG. If theirs no icon, it runs successful with signing.

Node: 8.12 MacOS High Sierra (10.13.6)

UPDATE: WOULD BE WILLING TO PAY SOMEONE TO FIX THIS ASAP.

dyld: lazy symbol binding failed: Symbol not found: __ZN4node19GetCurrentEventLoopEPN2v87IsolateE
  Referenced from: /Users/Musicline/Desktop/marks stuff/macos-packager/node_modules/fs-xattr/build/Release/xattr.node
  Expected in: flat namespace

dyld: Symbol not found: __ZN4node19GetCurrentEventLoopEPN2v87IsolateE
  Referenced from: /Users/Musicline/Desktop/marks stuff/macos-packager/node_modules/fs-xattr/build/Release/xattr.node
  Expected in: flat namespace

Just want to point out, ive already tried most of the obvious things, including delete node_modules and rebuilding, even set this up on a new project and same thing happened.

markmorris commented 5 years ago

No one?

LinusU commented 5 years ago

I'm sorry, I don't think I can be of much help here. Have you tried upgrading to a newer version of Node.js? Either the latest 8.x, or a 10.x release...

markmorris commented 5 years ago

yeah i tried literally all versions available. Kept throwing up the same error in slightly different format. Thanks for the reply, i will investigate more when i have the spare time.

candorco commented 5 years ago

Any progress with this? I'm having the same error

markmorris commented 5 years ago

Sorry no, i'm still getting the error if i try and change the icon.

recrsn commented 5 years ago

It's unfortunate that the NodeJS folks broke API in between releases. There is nothing much we can do in this regard. You can try npm rebuild fs-xattr

LinusU commented 5 years ago

It's unfortunate that the NodeJS folks broke API in between releases

Potentially this could be addressed in the future by moving to the N-API bindings, then it should be compatible between Node.js major releases. PRs welcome 🙌

simfer commented 5 years ago

I fixed it with npm rebuild bcrypt --build-from-source as reported here: https://github.com/kelektiv/node.bcrypt.js/issues/16

LinusU commented 5 years ago

I've converted node-xattr to use NAPI bindings instead of the v8 ones, so this should be resolved now!

Fixed in 🚢 0.6.0