Bug#1052486: jpeg-xl: FTBFS with libwebp 1.3.2: Use static libwebp library without linking libsharpyuv

[Boyuan Yang]

Source: jpeg-xl
Severity: serious
Version: 0.7.0-10
X-Debbugs-CC: malat at debian.org
Control: tags -1 +patch

Dear Debian jpeg-xl packager,

Unfortunately jpeg-xl in Sid now FTBFS more due to a corner case in searching of its
build-dependency libwebp.

In jpeg-xl CMakeLists.txt, it searches libwebp in order to build some test binaries.
Unfortunately the CMakeList.txt is hardcoding the logic to prefer static library if
present, and fall back to using shared library. However, with libwebp 1.3.x series,
the static library of libwebp also depends on symbols in libsharpyuv (which is built
together with libwebp). The building of jpeg-xl will unfortunately FTBFS if the static
libsharpyuv is not linked together with libwebp explicitly.

I am preparing a patch to solve this problem, which adds the logic of static libsharpyuv
linkage. Unfortunately this patch will be incompatible with libwebp (<< 1.3). The
alternative solution is to enforce dynamic linking at all time, which will be compatible
with all libwebp versions.

Thanks,
Boyuan Yang
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0007-tools-CMakeLists.txt-Fix-compatibility-with-static-l.patch
Type: text/x-patch
Size: 1097 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-phototools-devel/attachments/20230922/4ef6b94a/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-phototools-devel/attachments/20230922/4ef6b94a/attachment.sig>