[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Please test gub

From: Alexander Kobel
Subject: Re: Please test gub
Date: Thu, 31 Jan 2019 16:04:02 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0


On 31.01.19 13:25, Alexander Kobel wrote:
Indeed, pops up in the trace.
On my system, the symlink for already exists, so I only had to remove (rename wasn't enough)

Building tools::guile succeeds after that modification; I'll test the further progress of `make lilypond` later.

The build went on cleanly until poppler 0.49, which apparently is clever enough to figure out that it can't deal with my openjpeg installation ...

checking for LIBOPENJPEG... no
checking for opj_cio_open in -lopenjpeg... yes
checking openjpeg.h usability... no
checking openjpeg.h presence... no
checking for openjpeg.h... no

... but nevertheless insists on using it ...

Building poppler with support for:
  use libopenjpeg:     yes
      with openjpeg1

... and, to no surprise, fails:

/home/akobel/gub/gub/target/tools/src/poppler-0.49.0/poppler/ fatal error: openjpeg.h: No such
 file or directory
 #include <openjpeg.h>
compilation terminated.

FWIW, both openjpeg 1 and 2 are installed system-wide:

extra/openjpeg2 2.3.0-3 [installed]
    An open source JPEG 2000 codec, version 2.3.0
extra/openjpeg 1.5.2-2 [installed]
    An open source JPEG 2000 codec

and I can cleanly compile the recent poppler 0.73 with openjpeg2 backend from source, with a simple cmake + make.

Perhaps it's wise to disable openjpeg entirely for poppler within GUB? Note that, despite the name, openjpeg is only a concern for JPEG2000; plain old JPEG is supported by libjpeg. (BTW, can we actually add images in Lily?)


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]