FS#68855 - [python-grpcio] not usable : undefined symbol: RunningOnValgrind
Attached to Project:
Community Packages
Opened by Squalou Jenkins (squalou) - Saturday, 05 December 2020, 07:48 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Sunday, 06 December 2020, 10:28 GMT
Opened by Squalou Jenkins (squalou) - Saturday, 05 December 2020, 07:48 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Sunday, 06 December 2020, 10:28 GMT
|
Details
Description:
I do not know if it comes from upstream or not... as I don' know how to check. Using python module `grpc` is not possible, importing it raises an 'ImportError' due to undefined symbol in _cython .so file. (see error log below) Additional info: * package version(s) : python-grpcio-1.34.0-1 and python-grpcio-1.34.0-2 (maybe others) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: create a simple file ``` #!/usr/bin/python3 import grpc print("grpc") ``` run it see the error ``` import grpc File "/usr/lib/python3.9/site-packages/grpc/__init__.py", line 23, in <module> from grpc._cython import cygrpc as _cygrpc ImportError: /usr/lib/python3.9/site-packages/grpc/_cython/cygrpc.cpython-39-x86_64-linux-gnu.so: undefined symbol: RunningOnValgrind ``` |
This task depends upon
Closed by Massimiliano Torromeo (mtorromeo)
Sunday, 06 December 2020, 10:28 GMT
Reason for closing: Fixed
Additional comments about closing: 1.34.0-3
Sunday, 06 December 2020, 10:28 GMT
Reason for closing: Fixed
Additional comments about closing: 1.34.0-3
found a trace there :
src/abseil-cpp-20200225.2/absl/base/dynamic_annotations.cc:int RunningOnValgrind(void) {
On the other hand, installing (and building) the .so using a local python install, a virtualenv, and pip install => produces a working version of the .so file.
Which would tend to point to a packaging issue.
but ... can't be sure.
1.33.* and the PKGBUILD use abseil-cpp 20200225.2
1.34.* upstream uses abseil-cpp 20200923.2
https://github.com/grpc/grpc/commit/5b4344063e9d44cdd4e6f00729b48de2f2956145
Update: The version change builds a seemingly working package. At least the python module loads fine.
Should be fixed in 1.34.0-3
thanks for the fast fix!