Open vedeht opened 5 days ago
Usually this would be caused by make
not being available inside the docker environment. But if your build works with PyMuPDF-1.24.5, it might not be so simple.
Are you using the same docker image when building the two versions of PyMuPDF? If not, could you try building both PyMuPDF versions in the same docker image?
There is a difference in the make
command that is run between PyMuPDF-1.24.5 and PyMuDF-1.24.6 - PyMuDF-1.24.6 prefixes the command with XLIB_LDFLAGS=-Wl,-Bsymbolic
. I can't see why this would be a problem. It hasn't ever effected our standard builds and tests, but none of these uses docker.
I am using the exact same docker image. The only difference is 1.24.5 works and 1.24.6 does not work.
For me, the build passed without any issue, but when the container starts, was getting libmupdf.so 24.6 not found
and the container fails. Reverting back to 1.24.4
was my only solution.
Could you try building with PYMUPDF_SETUP_MUPDF_BSYMBOLIC=0
?
This will omit the new XLIB_LDFLAGS=-Wl,-Bsymbolic
setting, making the make
command more similar to that used by version 1.24.4.
Description of the bug
The Dockerfile failed to build because it couldn’t find the make command. This is indicated by the error message /bin/sh: 1: make: not found. The make command is essential for building the MuPDF library from source, which is a dependency for the pymupdf package.
I had to revert to version 1.24.5 to make this work
How to reproduce the bug
PyMuPDF version
1.24.6
Operating system
Linux
Python version
3.11