Il giorno dom 30 giu 2019 alle 10:45, Jean-Charles Malahieude
<lily...@orange.fr> ha scritto:
My first attempts were using the official Fedora package (as I do
since one is available), version 1.0.2. Facing this library problem,
I've built a package for 1.0.3 and then 1.1.0 which both bump the
wall.
Unfortunately, I don't remember if my last merge was just before
upgrading to Fedora 30 or not. And Federico, who runs a Fedora 30 as
well if I'm not mistaken, pushed on Translation mid-June…
Yes, I run Fedora 30 since it was released and I can compile lilypond
without any problem using the package available in Fedora.
I've now built the rpm for version 1.0.3 and it works as well. I'll
submit the new version to the Fedora repository soon. (I think 1.1.0
requires poppler>=0.74, which is not available in Fedora yet)
I think Masamichi analysis is correct.
You probably built the rpm when you had Fedora 29 and a different
version of poppler from what you currently have.
You could have checked it this way (after a new build from source you
already fixed it):
$ ldd /usr/bin/extractpdfmark | grep poppler
libpoppler.so.84 => /lib64/libpoppler.so.84 (0x00007f9a1930f000)
$ ls -l /lib64/libpoppler.so*
lrwxrwxrwx. 1 root root 16 30 mag 17.46 /lib64/libpoppler.so ->
libpoppler.so.84
lrwxrwxrwx. 1 root root 20 30 mag 17.46 /lib64/libpoppler.so.84 ->
libpoppler.so.84.0.0
-rwxr-xr-x. 1 root root 4831336 30 mag 17.46 /lib64/libpoppler.so.84.0.0
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
