Summary: | sys-apps/portage: soname dependency resolution does not distinguish bundled libraries from real providers (libOpenCL.so.1 should not be provided by nvidia-cuda-toolkit) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Zac Medico <zmedico> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | ionen, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 694246 |
Description
Zac Medico
![]() To distinguish this in iwdevtools' qa-vdb[1] (used to check missing dependencies by analyzing /var/db/pkg among other things), I've limited to libraries found through /etc/ld.so.conf paths to allow it to give the mostly-right suggestions, i.e. if linking against libOpenCL it'll say to add opencl-icd-loader rather than nvidia-cuda-toolkit Although being 100% correct and have it fit all setups may be difficult (may also have rpath using a different library with the same name and such) [1] https://github.com/ionenwks/iwdevtools#qa-vdb (In reply to Ionen Wolkens from comment #1) > also have rpath using a different library with the same name and such i.e. could imagine a scenario where path was gotten from pkg-config or something, and it's actually using libOpenCL provided by nvidia-cuda-toolkit and opencl-icd-loader could be depcleaned if nothing else uses it. |