Getting GLIBC version mismatch when using Pymupdf4llm(0.0.12) which tries to get Pymupdf 1.26.3 #4631
Unanswered
anjalig
asked this question in
Looking for help
Getting GLIBC version mismatch when using Pymupdf4llm(0.0.12) which tries to get Pymupdf 1.26.3
#4631
Replies: 1 comment
-
|
I'm afraid that the required glib version is outside of our control, and i can't suggest workaround other than to use a newer docker environment, or build pymupdf yourself. We build wheels using [I can't find a reference right now for how/when cibuildwheel's maintainers decide to update the manylinux build environment, but information might be on https://packaging.python.org somewhere.] |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm running an AWS Lambda function that performs text extraction using pymupdf4llm. It was working fine about a month ago, but now I'm encountering the following error during execution:
Runtime.ImportModuleError: Unable to import module 'app': /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /var/task/pymupdf/libmupdf.so.26.3)
It seems like something changed, possibly in a recent package release, but I'm not sure what. The Lambda environment itself hasn't been modified on our end.
In the build logs, I see:
Collecting pymupdf>=1.24.2 (from pymupdf4llm==0.0.12->-r requirements.txt)
Using cached pymupdf-1.26.3-cp39-abi3-manylinux_2_28_x86_64.whl.metadata
It appears that the latest version of pymupdf being installed now requires GLIBC 2.27, which isn't available in the default AWS Lambda runtime.
Has anyone else run into this issue? Are there recommended workarounds or resolutions?
Thanks in advance for any help!
Beta Was this translation helpful? Give feedback.
All reactions