-
-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation Problem when Installing Python Package (grpio) #45
Comments
@nickpresta: I don't think that linking to the glibc header files will help with compiling the Python
I'll have a further look into this issue today. |
Hey @sgerrand I hope things are going well with you. I just wanted to follow up and see if you had any time to take a look at this issue? Thanks! |
@nickpresta: Sorry that I haven't been able to help you with this issue. I'm not able to successfully compile the |
Hello,
I've moved the comments over from this PR.
Overview
I'm attempting to use the
glibc-dev
package, pulled from CircleCI's artifacts, but I'm getting strange problems when compiling thegrpio
package in Python.Here is a gist that provides a reproducible Dockerfile and the output I'm seeing.
This is very likely related to this issue filed with grpc.
Thanks to @jairov4 for trying to help. I added the gcc-libs that was suggested, but it didn't seem to fix anything (steps for this also included in the gist linked above).
Next Steps
What is confusing to me is that when I add the glibc-dev package and update the
CPATH
andLIBRARY_PATH
environment variables, I get an error on missingPython.h
, which suggests I'm missing the python-dev package, but it's installed. So I attempted to provide aCPATH
andLIBRARY_PATH
that would include the default locations as well as/usr/glibc-compat/lib
and/usr/glibc-compat/include
:But I still get the same problem about missing
Python.h
.When I remove all references to the
glibc-dev
directories when installing, I get the sameNo symbol version section for versioned symbol
memcpy@GLIBC_2.2.5'` error, which is obviously the original problem I'm hoping this package can solve.I understand that this may ultimately be a problem with the gRPC project and their interoperability with
musl
but I'm trying to understand if this issue is supposed to be fixed by this package.Thanks for the help!
The text was updated successfully, but these errors were encountered: