GLIBC library mismatch for Debian12

[Sahid]

Deploying OpenVino2025 on Debian12 - GLIBC library is mismatched. Debian does not have GLIBC2.38 - GLIBC2.36 is standard issue?

/usr/bin/ld: /opt/intel/openvino_2025.0.0/runtime/lib/intel64/libopenvino.so.2025.0.0: undefined reference to `__isoc23_strtol@GLIBC_2.38'

[Sahid]

After much tribulation and pain - trialing various OpenVino packages, ended up with a 2023.3 release working on Debian12. I also had to copy files around to make it all work ..

================from sync benchmark_app=============

INFO ] OpenVINO:
[ INFO ] Build ................................. 2023.3.0-13775-ceeafaf64f3-releases/2023/3
=============================

Please advise if/when we have a later version for Debian12 ..... when you have tested it and made sure all the scripts/libraries/respective compilers/directories/dependencies etc. work accordingly.

Cheers!

[Aznie_Intel]

Hi Sahid,

Thank you for reaching out.

Currently, Debian 12 is not officially supported for OpenVINO 2025. The issue you encountered is due to OpenVINO 2025 requiring GLIBC 2.38, while Debian 12 provides GLIBC 2.36 by default, causing compatibility issues.

At this time, the latest officially supported OpenVINO version for Debian-based systems is OpenVINO 2023.3, but even this version is not officially tested on Debian 12. While you may be able to run it with manual adjustments, stability is not guaranteed.

For a fully supported environment, we recommend using Ubuntu 22.04, which is officially tested and verified for OpenVINO 2025.

Regards,

Aznie

[Sahid]

Thank Aznie_Intel.

"....the latest officially supported OpenVINO version for Debian-based systems is OpenVINO 2023.3 ...." - we found out by trial and error.

"...but even this version is not officially tested on Debian 12. While you may be able to run it with manual adjustments, stability is not guaranteed......" - EULAs never guarantee anything ..:) ..:). We plan to shift to other distros.

Again, thanks.

[Aznie_Intel]

Hi Sahid,

This thread will no longer be monitored since this issue has been resolved. If you need any additional information from Intel, please submit a new question. 

Regards,

Aznie