Re: Please test gub

[Alexander Kobel]

Hi,

On 31.01.19 13:25, Alexander Kobel wrote:
> Indeed, LLVMgold.so pops up in the trace.
> On my system, the symlink for liblto_plugin.so already exists, so I only 
> had to remove (rename wasn't enough) LLVMgold.so.
>
> 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/JPEG2000Stream.cc:20:10: 
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?)


Cheers,
Alex

smime.p7s
Description: S/MIME Cryptographic Signature