Closed gifuzzz closed 3 years ago
Hi, you'll probably need to work out why the system runtime linker (and not sharp) is looking for shared libraries in /snap/core/current/lib/aarch64-linux-gnu/
before it looks in /lib/aarch64-linux-gnu/
.
Things to consider include: Is node
running via snap? Is it configured correctly? Could you have set a custom LD_LIBRARY_PATH
?
There are similar reports on unrelated bug trackers and repos so this is very likely to a problem with your local setup.
https://bugs.launchpad.net/snapcraft/+bug/1889409 https://github.com/microsoft/node-pty/issues/467
Is
node
running via snap?
Yes, it was running via snap. I removed it and installed from binary and now all works correctly!
I'm using ubuntu server 20.04 on a rapsberry pi 4. I installed sharp via
npm i sharp
, but when i require it, it gives me this:This is the output of
ldd --version
I have a little idea: sharp checks just the directory
/snap/core/current/lib/aarch64-linux-gnu/
in with the filelibm.so.6
is linked tolibm-2.23.so
, which is an older version. In/lib/aarch64-linux-gnu/
, instead, the filelibm.so.6
is linked tolibm-2.31.so
.