Closed slayoo closed 3 years ago
Thank you for looking into this!
It's a CentOS 7 machine. All the other package versions are correct.
hmm... not an uncommon problem :(
Oh wow. OK. If it turns out to be too big of a problem I can come back to trying to run it inside the Ubuntu Singularity image.
Sorry for being inactive recently. I don't have CentOS and the specific ABI. How about getting CUDA set up and building the code locally? Does it work it this case?
One down-side using CFFI(ABI mode) is that the building process doesn't really have an ABI check. The "AuditWheel" step is bypassed, which could cause a problem like this.
The lastest version 0.3.11, which I've just checked in to PyPi, is build using the Manylinux2010 docker image. Hopefully it will solve the issue.
Thank you! @trontrytel could you check if it helps on the CentOS 7 machine?
As reported originally here: https://github.com/atmos-cloud-sim-uj/PySDM/pull/513#issuecomment-840725954
We have a machine on which a fresh install of ThrustRTC using pip results in unusable package (Python 3.8.5, pip 20.3.1, ThrustRTC 0.3.10, cffi 1.14.5):
Some Googleing suggests that it is a glibc version incompatibility with the symbols used within the precompiled .so object shipped with pip, but then it should likely be reported by pip (i.e. pip should prevent from installing it), right?
Any hints? Thanks