libMagickCore.so.5 and libcfitsio.so.3 missing on upgrade to Ubuntu 15.04
See original GitHub issueWhen trying to use sharp on Ubuntu 15.04, I get errors about the absence of libMagickCore.so.5 and libcfitsio.so.3 (maybe because libmagickcore5 isn’t available in 15.04?)
Anyway, I was only able to get it working by linking to the libraries like so:
cd /usr/lib/x86_64-linux-gnu
sudo ln -sf libMagickCore-6.Q16.so libMagickCore.so.5
sudo ln -sf libcfitsio.so libcfitsio.so.3
Issue Analytics
- State:
- Created 8 years ago
- Comments:19 (7 by maintainers)
Top Results From Across the Web
Imagemagick won't run after upgrade to 15.04 - Ask Ubuntu
When upgrading to 15.04, the imagemagick dependency changed from libMagickCore.so.5 to 6-something. I uninstalled imagemagick, purged it, ...
Read more >Software Packages in "jammy", Subsection libdevel - Ubuntu
Qt library with support for bookmarks and the XBEL format. libkf5calendarcore-dev (5:5.92.0-0ubuntu1) [universe]: development files for kcalcore ...
Read more >Compare Packages Between Distributions - DistroWatch.com
accountsservice 22.07.5-2ubuntu1.3 ... indicator-datetime 15.10+21.04.20210304-0ubuntu1 ... libmagickcore-6.q16-6:amd64 8:6.9.11.60+dfsg-1.3build2
Read more >Debian -- Software Packages in "buster", Subsection libdevel
... files for the Allegro 5 library; liballjoyn-c-dev-1504 (15.04b+dfsg.1-3) ... High speed download utility (Development files); libaribb24-dev (1.0.3-2) ...
Read more >ChangeLog.openSUSE-Leap-15.4-x86_64-aarch64-ppc64le ...
So do not build for all python3.x flavors, + but only for the main one: + + Use ... with Plasma >= 5.21.3...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
yeah, fixing $PKG_CONFIG_PATH was the solution.
i managed it to crack that problem myself with this:
there is definitely a mess with the pkg configuration …