Closed mertalev closed 1 week ago
Those ENABLE_LIBDE265
and ENABLE_LIBSHARPYUV
should probably be WITH_x
- this got cleaned up.
I can't reproduce the failure locally. Possibly we aren't detecting the JPEG library (or lack of) correctly for this docker build.
Thanks for this tip!
The Dockerfile installs libjpeg62-turbo-dev before this. Maybe the error is related to this?
The error message seems to indicate that LIBJPEG_TURBO_VERSION_NUMBER
is defined to be empty.
I get the error only for a test program like this:
#define LIB123 123
#define LIBJPEG_TURBO_VERSION_NUMBER
#if defined(LIB123) && LIBJPEG_TURBO_VERSION_NUMBER == 2000000
If LIBJPEG_TURBO_VERSION_NUMBER
is not defined at all, I don't get that error.
That means that probably something is wrong with your libjpeg package. Search for that constant in the libjpeg header files and what it is set to.
I changed the Dockerfile to end at the previous build step and searched for LIBJPEG_TURBO_VERSION_NUMBER
. There are actually two entries:
root@2362ec38616b:/usr/src/app# grep -rnw '/usr' -e 'LIBJPEG_TURBO_VERSION_NUMBER'
/usr/local/include/jconfig.h:10:#define LIBJPEG_TURBO_VERSION_NUMBER
/usr/include/aarch64-linux-gnu/jconfig.h:10:#define LIBJPEG_TURBO_VERSION_NUMBER 2001005
The first one comes from jpegli, so it seems there's some kind of misconfiguration there.
I fixed it by adding -DLIBJPEG_TURBO_VERSION_NUMBER=2001005
to the libjxl build script's cmake command.
Thanks for the feedback.
Hi! I'm trying to upgrade my libheif build script from 1.18.2 to 1.19.3, but encountered this error:
libheif is built with this command:
This is the specific GitHub workflow that failed.