Hi all.
After finally getting 4.6 compiled from source a couple of days ago with help from some of you awesome legends, I have now run into another snag.
I just fired up manjaro, was prompted that there were a bunch of updates for my system, and let pamac go ahead and do its thing. After it had installed the updates, it told me a restart was required, so I restarted.
Went to launch dt from my shortcut, and it wouldn’t start.
I thought “that’s weird”, so I went to the command line and tried launching it from there, only to be presented with:
/opt/darktable/darktable-4.6/bin ./darktable --configdir ~/.config/darktable/4.6/
./darktable: error while loading shared libraries: libicui18n.so.73: cannot open shared object file: No such file or directory
Now, I don’t know for sure, but my guess is that somehow this library got messed with during my updating of the rest of the system.
I tried searching for ‘libicui18n.so.73’ in pamac, but found nothing.
Anyone able to point me in the right direction here, please?
Thanks in advance!
Bruce, can you use the darktable-git pkgbuild on the AUR (e.g. along with a program like pacaur) to make it easier to recompile? At least for me on Arch I’m able to run pacaur -S darktable-git and compile packages from the AUR easily
Beware that running darktable-git from the AUR will mean you are always tracking the latest master build and not the latest stable release, and you can’t go back to stable once you’ve started using development, without some effort and potentially losing some edits.
You’re right, these instructions are for anyone who wants to track the latest development release. Bruce, if you want to instead stay on the stable release only, you shouldn’t need to compile it yourself once the darktable 4.6 binary package in the official Arch repos (currently in the Extra-Testing repo) is promoted to the Extra repo. I imagine once it ends up in Extra in Arch it will shortly thereafter appear as a package in Manjaro and then you can just install it without needing to manually compile it.
Anyway, instructions for building the latest development release (note that I run Arch and not Manjaro so it’s possible these instructions could vary):
ensure you’re fully up-to-date with sudo pacman -Syu
install the newly-built binary package: sudo pacman -U darktable-git-*.pkg.tar.zst
You can keep a copy of this .pkg.tar.zst file around to easily re-install darktable later too. This is a frozen point-in-time build of the development branch, but you should be able to repeat these steps whenever you want to build a new binary package (and install it) to update again later.
Andrew, thanks for the instructions.
I have however, in the last 24 hours, decided to move on from manjaro. Having it break my installation every couple of days is doing my head in.
And yes, I DO wish to follow the development version. It enables me to get up to speed on new features as they are added, and that means that when a new version drops, I’m ready to create content around it, AND actually have an idea of what I’m talking about!
Fair enough. I will say don’t let one bad experience dissuade you from the rolling release model though; if implemented well, it can work very smoothly with minimal overhead.
I’m sure manjaro is great, for those that understand it.
But I am not geeky enough to have wrapped my head completely around it, and having to recompile and reinstall darktable every couple of days because of system updates that have broken it… that’s a price I am not willing to pay.
Can you walk me through that step by step?