-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Debian Wheezy: sharp breaks if the canvas module is loaded first #371
Comments
I suspect In this case, it's probably best to follow suit and use a system-wide install of libvips. |
I got this issue too on Ubuntu 14.04.
Sharp ran fine before I installed the canvas. |
Quick thought: are either of you able to try using the fully-versioned path to the shared library (rather than the partial-versioned symlink) in the libraries section of binding.gyp, something like: - '<(module_root_dir)/lib/libglib-2.0.so',
+ '<(module_root_dir)/lib/libglib-2.0.so.0.4705.0', - '<(module_root_dir)/lib/libgio-2.0.so',
+ '<(module_root_dir)/lib/libgio-2.0.so.0.4705.0', Failing this, the only option I can think of is to experiment with the |
Another even quicker thought: LD_PRELOAD=/path/to/node_modules/sharp/lib/libglib-2.0.so node script.js ...should make sharp's bundled glib take precedence regardless of module import order. |
Sorry for not reporting back earlier. I just switched around the
... and then it hangs. If I make the suggested patch to
|
@papandreou Thanks for checking. I guess the dependencies of glib would also need to be included in the @nsmag Were you also able to "fix" this by altering the |
@lovell Sorry for not reporting back. I'll experiment with canvas + sharp again later. Sharp is lightning fast! |
Glad you both found workarounds. I'll close this for now but please feel free to comment and/or re-open with any more quick fix solutions :) |
I was getting the same |
I did experiment with the |
Any progress to solve this incompatible problem? I got the same error when I uses both sharp and node-canvas |
When I require |
@jingsam If you're relying on a system-wide installation of |
I ran into this very puzzling issue on Debian Wheezy, which I haven't been able to repro on my workstation, which runs a much newer Ubuntu.
It goes something like this:
Interestingly it does not blow up if the two
require
s are reversed!It's reproducible with both node.js 0.10.38 and 4.3.1. Haven't tried any others.
Any ideas?
The text was updated successfully, but these errors were encountered: