-
Notifications
You must be signed in to change notification settings - Fork 85
Lumo crashes when requireing packages with .node binary #163
Comments
@hlolli Sorry, this regression was introduced in this commit, and should be a very simple fix. Do you want to put a PR together fixing it? |
Yup, I will look into this. Just getting used to setting up the dev env, been waiting 2 hours for |
@hlolli |
lol, so I've been waiting for nothing. ehm.. how do you start lumo without creating a binary :/ ? |
But this will run under an actual Node.js. To debug this particular problem you'll need to create a binary. Thankfully the fix for this issue is simple: literally revert the change I linked above. |
fixed 7ea440a |
Any chance we could get a release for this? |
I can make a release, but would a link to a nightly build suffice for your immediate needs? |
Yeah, that would be fine. |
This is still a problem for me from the latest Lumo nightly
getting segfaults from (js/require "pacage-using-gyp-or-.node") |
Does not happen when I run lumo like this |
@hlolli this seems odd but I'll reopen. Can you provide the name of a package that fails to execute? |
My importance is with csound-api for my live-coding environment, but that requires csound to be installed. You can try requireing I built lumo and the binary fails, it differentiates from the nightly build, which gives me segfault, my build just causes the terminal to freeze. |
I can repro this on Ubuntu. I think the problem might be related to Lumo being statically linked, while the native packages are compiled with a different libc version. |
fixed in #176 |
After updating to lumo 1.5, packages that are running with .node binaries won't work, more specifically gyp built modules. In my case I'm using csound-api which requires csound and boost to be installed, but another reproduce-able example can be created if require-ing "netlinkwrapper": "1.0.0".
$ lumo
cljs.user=> (js/require "netlinkwrapper")
crash
These modules can be required with node 7.10.0 without crash.
The text was updated successfully, but these errors were encountered: