Summary: | dev-libs/rocm-device-libs-5.7.1 clang can't find amdgcn/bitcode automatically | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sv. Lockal <lockalsash> |
Component: | Current packages | Assignee: | Craig Andrews <candrews> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | lockalsash, negril.nx+gentoo, xgreenlandforwyy |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugzilla.redhat.com/show_bug.cgi?id=2209759 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sv. Lockal
2024-01-16 15:04:52 UTC
https://github.com/negril/gentoo/tree/sys-libs/libomp/fix_offload_install_location This is somewhat related Please share your opinions. My suggestion is to move /usr/lib/amdgcn to /usr/lib/clang/17/amdgcn, and don't provide any symlinks, as they are not needed. I think the cleanest way to do it with all dev-libs/rocm-device-libs ebuilds (but it requires to check which other ebuilds have patches for setting --rocm-path and --rocm-device-lib-path to old path). The simpler solution is to provide a symlink in <=5.7.1, and in 6.0.0 remove the symlink. It looks that many 6.0.0 HIP/ROCm packages have hard dependency for 6.0.0 toolchain, so it should be safe. What do you think? (In reply to Sv. Lockal from comment #2) > Please share your opinions. My suggestion is to move /usr/lib/amdgcn to > /usr/lib/clang/17/amdgcn, and don't provide any symlinks, as they are not > needed. > I agree to move /usr/lib/amdgcn to /usr/lib/clang/17/amdgcn. dev-libs/rocm-device-libs is essentially part of llvm-project that somehow does not upstreamed. > I think the cleanest way to do it with all dev-libs/rocm-device-libs ebuilds > (but it requires to check which other ebuilds have patches for setting > --rocm-path and --rocm-device-lib-path to old path). Yes, that's cleaner. However, that means simultaneous revision bump of rocm-device-libs and all revdeps, which it means some user may upgrade one package, not the other one, and cause regression, so we need to set a min revision dependency for hip. > > The simpler solution is to provide a symlink in <=5.7.1, and in 6.0.0 remove > the symlink. It looks that many 6.0.0 HIP/ROCm packages have hard dependency > for 6.0.0 toolchain, so it should be safe. So I prefer this. |