Hi, On 5/15/26 10:17, xiao sheng wen(肖盛文) wrote:
I just had a look at why libjxl-devtools and libjxl-tools don't reproduce and it seems to capture the CPU features of the host where the build runs and embeds it in the binary. Could you have a look and avoid it? If it would actually uses these results, your package would very likely be violating the Debian baseline for amd64 too.In libjxl-devtools and libjxl-tools packages, also has binary CLI: /usr/bin/cjxl /usr/bin/djxl /usr/bin/benchmark_xl These command files had passed reproduce build, they are identical in different build host, so they don't capture the CPU features of the host where the build runs and embeds it in the binary.
That's indeed what I tried to convey.
The question is the man which generated by help2man.
Agree.
The jpeg-xl source package build depend the libhwy-dev, it's source package is highway. ldd /usr/bin/benchmark_xl |grep hwy libhwy.so.1 => /usr/lib/x86_64-linux-gnu/libhwy.so.1 (0x00007fbe70295000) As far as I know, the highway so library libhwy.so.1 will auto detect the CPU SIMD/vector instructions which program run on. benchmark_xl,cjxl,djxl --help will print the CPU SIMD/vector instructions information which get from libhwy.so.1. About this bug, How to fix it? Welcome supply some suggestions. Patch is also welcome.
If you can't figure out anything better (e.g. prevent the instruction information from appearing in the help text via options or ENV variables), I suggest to post-process the text to strip out or replace the instruction set text. Not particularly pretty, but should be extremely effective without much harm.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
