Dear Maintainer,

the package in experimental fails to build (see e.g.
https://buildd.debian.org/status/fetch.php?pkg=jpeg-xl&arch=i386&ver=0.11.1-1&stamp=1739052249&raw=0).
While I it is probably not the best way to fix it, not enabling LTO
makes it build for me.


Best regards,
Julian
--- jpeg-xl-0.11.1/debian/rules	2025-02-06 18:42:30.000000000
+0100 +++ jpeg-xl-0.11.1_fixed/debian/rules	2025-03-09
12:00:42.249586914 +0100 @@ -7,7 +7,7 @@ ifeq
($(DEB_HOST_ARCH),$(filter $(DEB_HO export CC=gcc-13
   export CXX=g++-13
 endif
-export DEB_BUILD_MAINT_OPTIONS = hardening=+all optimize=+lto
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all

 # keep same order as
https://buildd.debian.org/status/package.php?p=google-perftools&suite=sid
 # purposely remove i386 for Ubuntu compat

Thank you for figuring out a workaround. I pushed the requested change.

I originally opted into LTO because Ubuntu enables it by default and
it allowed us to synchronize the symbols file more easily. But I
pushed a commit to mark the additional symbols as optional.

I am surprised that this issue only affected Debian (Experimental?)
but didn't affect Ubuntu 25.04 which is fairly similar.

I made a very late request now to start the jpeg-xl 0.11 transition.
It overlaps the ongoing icu 76 transition so I don't know whether the
Debian Release Team will give us permission.
https://bugs.debian.org/1100535

Could you try reporting the LTO issue upstream?
https://github.com/libjxl/libjxl/issues

Thank you,
Jeremy Bícha