Dynamically linked python fails to find its shared lib file #139
Labels
Comments
|
@tkamenoko Can you try the following things? That would help me diagnose the problem. Use LD_LIBRARY_PATH manuallyI believe running this should work: Running lddCan you run and paste the output of the following two commands: ldd ${HYGEIA_HOME}/installed/cpython/3.8.1/bin/pythonLD_LIBRARY_PATH=${HYGEIA_HOME}/installed/cpython/3.8.1/lib ldd ${HYGEIA_HOME}/installed/cpython/3.8.1/bin/pythonGet compilation configsAssuming the above works, can you paste the output of this: LogsI'd also be interested in the logs found under I've pushed a dockerfile for debian sid to try to reproduce the problem (which I still can't). You can inspect it here: https://github.com/nbigaouette/hygeia/blob/master/docker/debian/sid/Dockerfile You can also try it yourself: > export SERVICE_NAME=debian_sid
> docker-compose build ${SERVICE_NAME}
> docker-compose run --rm ${SERVICE_NAME} |
|
@nbigaouette thank you for the investigation! Here are the results. Environment
Use LD_LIBRARY_PATH manuallyRunning ldd |
Get compilation configs |
|
Thanks for the details! Some observations from them:
Googling this a bit, there is an open issue with ld.gold ignoring the environment variable:
I'll try to verify this hypothesis using a VM with NEON 5.17. If that is actually the issue, I might replace using |
|
I've tried to run a docker image that should be close to your setup: From it inside it I've installed hygeia 0.3.1: Then install python 3.8.1: The resulting python binary can properly find its own I then It seems that by default Did you changed something to use the gold linker? I changed the link to use the gold linker and recompiling to see if I can reproduce... |
|
Using the gold linker seems to have ignored the |
|
@nbigaouette I used Thanks for your hard work! |
|
Fantastic! I'll create a dockerfile for neon and will try to reproduce with linuxbrew. I think that I'll change The other workaround would be to compile python twice. Once with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #122 @tkamenoko reported a problem:
I think this is a different issue than #122 so opening a new bug to track it.
I'm having difficulty reproducing this though. Using a debian (
sid-20191224) docker container I could not reproduce the issue.libpython3.8.so.1.0is properly found:The text was updated successfully, but these errors were encountered: