>>> package: sys-libs/binutils-libs-2.40-r1 * - /usr/lib64/libbfd-2.37.gentoo-sys-libs-binutils-libs-mt-def.so * used by /usr/lib64/libmca_common_ucx.so.40.30.2 (sys-cluster/openmpi-4.1.4) * used by /usr/lib64/openmpi/mca_atomic_ucx.so (sys-cluster/openmpi-4.1.4) * used by /usr/lib64/openmpi/mca_osc_ucx.so (sys-cluster/openmpi-4.1.4) * used by /usr/lib64/openmpi/mca_pml_ucx.so (sys-cluster/openmpi-4.1.4) * used by /usr/lib64/openmpi/mca_spml_ucx.so (sys-cluster/openmpi-4.1.4) * used by /usr/lib64/openmpi/mca_sshmem_ucx.so (sys-cluster/openmpi-4.1.4) This is a result of ucx linking against libbfd. openmpi components that link against ucx directly link any of its dependencies as well. Since ucx has USE=numa, and this results in ucx libraries linking against libnuma, this presents a similar problem since it's possible to build ucx with numa, build openmpi, and then rebuild ucx without numa and get preserved libraries. (I think the only solution to this is for openmpi to have a dependency on sys-cluster/ucx[numa].) (Really openmpi needs to directly depend on /anything/ ucx links against.) Reproducible: Always
Still seeing this with sys-cluster/openmpi-4.1.6 after a sys-libs/binutils-libs update: >>> package: sys-libs/binutils-libs-2.42-r1 * - /usr/lib64/libbfd-2.41.0.gentoo-sys-libs-binutils-libs-mt-def.so * used by /usr/lib64/libmca_common_ucx.so.40.30.2 (sys-cluster/openmpi-4.1.6) * used by /usr/lib64/openmpi/mca_atomic_ucx.so (sys-cluster/openmpi-4.1.6) * used by /usr/lib64/openmpi/mca_osc_ucx.so (sys-cluster/openmpi-4.1.6) * used by /usr/lib64/openmpi/mca_pml_ucx.so (sys-cluster/openmpi-4.1.6) * used by /usr/lib64/openmpi/mca_spml_ucx.so (sys-cluster/openmpi-4.1.6) * used by /usr/lib64/openmpi/mca_sshmem_ucx.so (sys-cluster/openmpi-4.1.6)