Closed igozali closed 1 year ago
The use case for this is if we're operating on a cluster computing system where we don't easily have root access, upgrading the Ubuntu OS (to get a newer glibc) is a rather slow process and we often have to install things in userspace, e.g. the solution provided by this gist: https://gist.github.com/michaelchughes/85287f1c6f6440c060c3d86b4e7d764b
Another thing I was wondering: since conda
knows the version of the system's glibc, is it possible to have the opencv
package build process incorporate the glibc
version in the version compatibility checks.
Those errors are related to C++ symbols, so libstdcxx, not glibc . Are you sure that your process is loading conda-forge's libstdcxx and not for some reason the system one?
My bad, thanks for the clarification and suggestion. We've actually been using system libstdcxx, glibc
to build additional Python extensions on top of the shared libraries we download from conda.
In the past, I've wanted to use the build toolchain that comes from the conda environment instead of system build toolchain, but I had some issues because conda's build toolchain is configured as a cross-compiler (asked in Gitter) as well.
I will try to pick up libstdcxx
from conda-forge and see how that goes!
Seems to work, I will close the issue. Thanks again for the help!
Comment:
I was wondering if there's a good way to install more recent
opencv
packages from conda-forge on older Ubuntu versions e.g. 20.04? The primary issue seems to be theglibc
version, where I would be encountering these kinds of issues:The above happens with this version of opencv:
In Ubuntu 20.04, the highest glibc version we can install from
apt
is 2.31 (without resorting to tricks like compiling our own glibc andpatchelf
shenanigans).Here's some mamba info printouts from my system: