Current versions don't support multilib try to use the wrong library directory resulting in failing emerge process.
Please include the build.log and emerge --info.
Created attachment 894614 [details] emerge --info
Created attachment 894615 [details] experimental ebuild update
Added experimental updated multilib ebuild that doesn't find LLVMSPIRVLib
Created attachment 894616 [details] build.log
Why would this package need multilib support? It installs a single binary for the native ABI that is used by the build of Mesa for each ABI.
The native ABI install obviously doesn't recognize the library directory configuration. Probably changing the meson libdir should be enough to get the effeccts of GNUInstallDirs in CMake
Yes, but you're going down the wrong path. We need to figure out why the vanilla ebuild in ::gentoo doesn't work. multilib makes no sense for this package.
(In reply to Jon Daniel from comment #7) > The native ABI install obviously doesn't recognize the library directory > configuration. Don't you think that if that was the problem, that it would still fail to build the native ABI binary?
temporarily removing 32-bit libz.* in /usr/lib as a workaround successfuly completes inteL_clc emerge. rm /usr/lib/libz.* && emerge -v intel_clc::gentoo && emerge -v zlib
The bug is reproduceable and not resolved or invalid
I think you need to start inspecting /usr/lib64/pkgconfig/*.pc. E.g. > grep -r -- 'usr/lib$' /usr/share/pkgconfig /usr/lib64/pkgconfig
Also grep your intel_clc build directory for `/usr/lib/libz.so` after running `sudo ebuild intel_clc-24.1.0.ebuild clean install`.
The error occurs with media-libs/mesa-24.1.0-r1 too which supports multilib. This time I am not able to merge it with just removing the /usr/lib/libz.*
Latest updates to 24.1.1 didn't fix the problem
(In reply to Jon Daniel from comment #14) > The error occurs with media-libs/mesa-24.1.0-r1 too which supports multilib. > This time I am not able to merge it with just removing the /usr/lib/libz.* This is because the problem has nothing to do with support for multilib or lack thereof. (In reply to Jon Daniel from comment #15) > Latest updates to 24.1.1 didn't fix the problem This makes sense because the problem is almost certainly something specific to your local machine.
It's been fun.
You likely have some junk in /usr/local or some odd environment variable set (check `env`). Otherwise, this is better debugged in a support forum.
As a workaround disable 32-bit multilib ABI for mesa and delete /usr/lib/libz.*
