You are not logged in.
Hi,
no idea where to post this so I give a try here, it's the closest match.
Since python update to 3.9, I face this issue with grpc
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
I uninstalled / reinstalled python grpcio and grpcio-tools (from aur : sometimes rebuild help, not here)
ldd /usr/lib/python3.9/site-packages/grpc/_cython/cygrpc.cpython-39-x86_64-linux-gnu.so
did show
$ ldd /usr/lib/python3.9/site-packages/grpc/_cython/cygrpc.cpython-39-x86_64-linux-gnu.so
linux-vdso.so.1 (0x00007fff59309000)
libssl.so.1.1 => /usr/lib/libssl.so.1.1 (0x00007f48a6383000)
libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0x00007f48a60a5000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f48a608b000)
libcares.so.2 => /usr/lib/libcares.so.2 (0x00007f48a6072000)
libre2.so.8 => /usr/lib/libre2.so.8 (0x00007f48a6009000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f48a5fe7000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f48a5e08000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007f48a5cc2000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f48a5af9000)
/usr/lib64/ld-linux-x86-64.so.2 (0x00007f48a6883000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f48a5af3000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f48a5ad9000)
and all these files do exist ... and I don't what what more to check.
Any advice will be welcome !
thx
Last edited by squalou (2020-12-06 07:55:29)
Offline
grpc was updated to 1.34.0-1 just a few hours ago.
Does 1.34 version also have this problem ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
to make sure we talk about the same thing : package is python-grpcio (there is a grpc package too).
I did uninstall all I could, checked python3.9/site-pacakges did not contain any grpc* thing
Installed again : python-grpcio and python-grpcio-tools
Still getting the same error.
In the meantime, note that I did
- create a local installation of python3.9 (using pyenv)
- made a virtualenv and activated it
- installed python-grpcio an tools with pip there
-> it works. So, I have a local workaround but that's not a clean durable solution
That's weird.
in /usr/lib/python3.9/site-packages/grpc/_cython file cygrpc.cpython-39-x86_64-linux-gnu.so is 4,2M
in my virtualenv, it's 9.0 M. But ldd shows less things ... so I guess things are hard linked inside instead of using dynamically shared objects
for the records
linux-vdso.so.1 (0x00007ffd56d87000)
librt.so.1 => /usr/lib/librt.so.1 (0x00007fa21cd66000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007fa21cd44000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fa21cb67000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007fa21ca21000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007fa21c858000)
/usr/lib64/ld-linux-x86-64.so.2 (0x00007fa21d504000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007fa21c83e000)
Last edited by squalou (2020-12-04 19:44:45)
Offline
to reproduce, edito a file containing
#!/usr/bin/python3
import grpc
print("grpc")
chmod +x and run.
See error
=> probably bug in package, I'll try to report an issue there (package python-grpcio-1.34.0-2 has the same issue)
Last edited by squalou (2020-12-05 07:32:47)
Offline
for the records, I installed the packages listed in PKGBUILD as required to build python-grpcio package : does not fix the issue either.
Rebuilding from PKGBUID does not fix anything either, produced .so file is still providing same error. Probably upstream issue.
Last edited by squalou (2020-12-05 11:01:01)
Offline
Same problem here running a flask app.
I am wondering if we need to open a bug report at bugs.archlinux.org or if it's an upstream bug an raise an issue in https://github.com/grpc/grpc ?
Downgrading package to 1.33.2-3 works fine.
Last edited by solstice (2020-12-05 15:39:22)
Offline
Same problem here,
reverted to 1.33 version from archive.
Thanks for bug report
1.34.0-1 same problem for me
Last edited by Ernestosparalesto (2020-12-05 16:07:03)
Offline
Here is a wild guess: Maybe the maintainer did not compile the package in a clean chroot, but in a dirty system that had a python build with valgrind enabled.
Last edited by progandy (2020-12-05 17:47:11)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
devtools rejects packages not built in a chroot.
Offline
By the way, here is the related bug report: https://bugs.archlinux.org/task/68855
The problem appears to be an old version of the abseil-cpp submodule.
Last edited by progandy (2020-12-05 17:49:22)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Sorry I'm back here a bit late : yeah I opened the bug report.
Should I close this thread, or wait for the bug to be solved first ? No Idea what is the recommended practice.
Offline
Fixed in 1.34.0-3
Offline