-
Notifications
You must be signed in to change notification settings - Fork 150
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
Repaired wheel can't find some of its included libraries #416
Comments
Could you upload the bad wheel somewhere, or provide instructions to reproduce the issue? |
If you try with the previous version |
It seems that the
Stripping the
I thought auditwheel stripped the @OKaluza I tried building the project here but it failed with a compiler error. I can give it another go when I get more time, but if you could upload the unrepaired wheel somewhere, that would help. |
Ah sorry about that, attempting to prepare for distutils being deprecated and broke things, build should be fixed now. |
Thanks. I just checked this and I cannot reproduce the issue when repairing this wheel. I am repairing it for
However, libLLVM is not in the wheel. How exactly do you run auditwheel to get the libLLVM dependency vendored? I took a look at the GH actions in the project but couldn't see anything relevant. I have the following files in lavavu_osmesa.libs:
This is a much smaller set of libraries than in the wheel on PyPI so there is probably a difference in library dependencies in the build environment. |
Sorry my mistake, it seems libOSMesa wasn't installed anymore on the machine I built it on, I rebuilt the wheel and it definitely links to libLLVM now: https://github.com/lavavu/LavaVu/releases/download/1.8.45/lavavu_osmesa-1.8.45-cp311-cp311-linux_x86_64.whl
The build command was: |
Hi, thanks for this really useful software. Unfortunately some of my wheel builds using cibuildwheel 2.12.1 with auditwheel 5.3.0 are broken and I can't find a way to fix them without manually patching the wheel or requiring LD_LIBRARY_PATH to be set:
Testing the package:
Running ldd on the module shows three libraries not found:
Yet, inspecting rpath is correct and ls shows the libraries exist there:
None of these libraries are direct dependencies of my module, they seem to be dependencies of other dependencies (probably from libOSMesa as my main package/module without this library works fine). It seems those libraries aren't able to find their own dependencies in the same directory.
I can get around the issue by setting
LD_LIBRARY_PATH=${HOME}/python-default/lib/python3.10/site-packages/lavavu_osmesa.libs
or runningpatchelf --force-rpath --set-rpath '$ORIGIN' *.so*
in the lavavu_osmesa.libs directory but I'd like a permanent fix in the wheel.Am I doing something wrong or is this a bug? Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: