Re: zathura-pdf-mupdf: undefined symbol: opj_setup_decoder

[lemmi <lemmi@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]

New comment by lemmi on void-packages repository

https://github.com/void-linux/void-packages/issues/35634#issuecomment-1240548064

Comment:
> I think this might be the offending change: https://git.pwmt.org/pwmt/zathura-pdf-mupdf/-/blob/0.3.8/meson.build#L32-36
> 
> If you modify the `meson.build` such that the `else` block always executes, I think you might be able to get it to build.

Yeah, this is basically what we achieved by not updating to `0.3.8`. That obviously won't work forever.

So, [comments for 49a85ef](https://git.pwmt.org/pwmt/zathura-pdf-mupdf/-/commit/49a85efb915bfed933d251f6074b807d0e1ef385#note_1588) sound like this won't be fixed by upstream at this point, but they are open to contributions. Additionally they suggested 
1. to rework the detection, such that they can still run their tests against `mupdf` built from source
2. ship a `pkgconfig` file with `mupdf-devel`
   Maybe @Gottox can judge whether this is possible or desired

I don't know how to do either of those, but I think we can just revert [49a85ef](https://git.pwmt.org/pwmt/zathura-pdf-mupdf/-/commit/49a85efb915bfed933d251f6074b807d0e1ef385) for the time being and keep the thing on life support this way for a little longer.