build problem

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

build problem

Jean-Charles Malahieude-2
Hello,

Since I can't get a successful doc-build on my Fedora 30 box, I'm unable
to check doc-changes and merge translation into stable.

It's the same with extractpdfmark 1.0.2 1.0.3 and 1.1.0

log spits:

extractpdfmark -o ./out-www/collated-files.pdfmark
./out-www/collated-files.tmp.pdf
extractpdfmark: error while loading shared libraries: libpoppler.so.78:
cannot open shared object file: No such file or directory

And I won't try to package poppler-0.78. There are too many dependencies
for me (Fedora is stuck to 0.73).

Cheers,
--
Jean-Charles

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: build problem

Masamichi HOSODA-2
> Hello,
>
> Since I can't get a successful doc-build on my Fedora 30 box, I'm
> unable to check doc-changes and merge translation into stable.
>
> It's the same with extractpdfmark 1.0.2 1.0.3 and 1.1.0
>
> log spits:
>
> extractpdfmark -o ./out-www/collated-files.pdfmark
> ./out-www/collated-files.tmp.pdf
> extractpdfmark: error while loading shared libraries:
> libpoppler.so.78: cannot open shared object file: No such file or
> directory
>
> And I won't try to package poppler-0.78. There are too many
> dependencies for me (Fedora is stuck to 0.73).

In Fedora 30, I suggest to use extractpdfmark from package,
rather than self-built extractpdfmark.
https://apps.fedoraproject.org/packages/extractpdfmark

If I understand correctly,
Fedora 30 has popler-0.73.0 package that has libpoppler.so.84.
https://koji.fedoraproject.org/koji/rpminfo?rpmID=17656985
Fedora 29 has popler-0.67.0 package that has libpoppler.so.78.
https://koji.fedoraproject.org/koji/rpminfo?rpmID=17657086

Did you build extractpdfmark on Fedora 29?
If so, it depends on libpoppler.so.78.
However, Fedora 30 does not have libpoppler.so.78.

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: build problem

Jean-Charles Malahieude-2
Le 30/06/2019 à 02:51, Masamichi Hosoda a écrit :

> In Fedora 30, I suggest to use extractpdfmark from package,
> rather than self-built extractpdfmark.
> https://apps.fedoraproject.org/packages/extractpdfmark
>
> If I understand correctly,
> Fedora 30 has popler-0.73.0 package that has libpoppler.so.84.
> https://koji.fedoraproject.org/koji/rpminfo?rpmID=17656985
> Fedora 29 has popler-0.67.0 package that has libpoppler.so.78.
> https://koji.fedoraproject.org/koji/rpminfo?rpmID=17657086
>
> Did you build extractpdfmark on Fedora 29?
> If so, it depends on libpoppler.so.78.
> However, Fedora 30 does not have libpoppler.so.78.
>

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…


Cheers,
--
Jean-Charles

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: build problem

Knut Petersen
On 30.06.19 10:45, Jean-Charles Malahieude wrote:
>
> 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…
>
Build it yourself. Building and installing extractpdfmark is  an easy an fast task.
Cloning the repository, building, testing and installing of extractpdfmark takes
less than 20 seconds here:

    git clone https://github.com/trueroad/extractpdfmark.git && \
    cd extractpdfmark && \
    ./autogen.sh && \
    mkdir build && \
    cd build && \
    ../configure && \
    make && \
    make check && \
    sudo make install


If building fails: Have a look at extractpdfmark/README.md - there you find a list of required packages.

Knut
_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: build problem

Jean-Charles Malahieude-2
Le 30/06/2019 à 11:10, Knut Petersen a écrit :
> Build it yourself. Building and installing extractpdfmark is  an easy
> an fast task.
> Cloning the repository, building, testing and installing of
> extractpdfmark takes less than 20 seconds here:
>

This, as intended, works like a charm, but I was expecting an rpm to do
its job (and notice nothing wrong when creating them).

Cheers,
--
Jean-Charles

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: build problem

Federico Bruni-2
In reply to this post by Jean-Charles Malahieude-2
Il giorno dom 30 giu 2019 alle 10:45, Jean-Charles Malahieude
<[hidden email]> 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
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: build problem

Federico Bruni-2
Il giorno lun 1 lug 2019 alle 8:03, Federico Bruni <[hidden email]>
ha scritto:
> 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)

Jean-Charles, version 1.0.3 is now available in Fedora 30 repositories.
And version 1.1.0 is in rawhide.



_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: build problem

Jean-Charles Malahieude-2
Le 26/07/2019 à 09:44, Federico Bruni a écrit :
> Jean-Charles, version 1.0.3 is now available in Fedora 30 repositories.
> And version 1.1.0 is in rawhide.
>

As I've cloned the repository and built it without any problem,
everything is fine.

Cheers,
Jean-Charles

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel