The package needs to be split, one for the latest runtime, one for the legacy. https://gitlab.archlinux.org/archlinux/packaging/packages/intel-compute-runtime/-/issues/3 OpenCL doesn't work anymore on my Intel HD Graphics 530 (Skylake), attempt to build a program crashes the process with the message: RequiresExtension: Feature requires the following SPIR-V extension: SPV_KHR_non_semantic_info
I don't maintain this but I don't think this would be viable for long, these packages already gives a lot of headaches (esp. for a source based distro that needs to keep them compiling with modern toolchains) and keeping a version that is no longer supported upstream would likely fall apart rather quickly.
(In reply to Ionen Wolkens from comment #1) > no longer supported upstream Or is there a legacy branch that is still receiving support? May have misunderstood.
Looks like there is a legacy branch that will receive no new features, but critical fixes only: https://github.com/intel/compute-runtime/blob/master/LEGACY_PLATFORMS.md
FWICS, the current version in tree seems the legacy branch and newer versions dropped support. I would tend to introduce a legacy slot instead of multiple variant packages. WDYT?
(In reply to Conrad Kostecki from comment #4) > FWICS, the current version in tree seems the legacy branch and newer > versions dropped support. Not quite, the current package version is 24.35.30872.25, while the first runtime release that dropped legacy support runtime is 24.35.30872.22. > I would tend to introduce a legacy slot instead of multiple variant > packages. WDYT? Any solution that works is fine by me. It is unlikely that two branches can be installed at the same time, nor that somebody has such hardware configuration in the first place.
(In reply to Ivan Podmazov from comment #5) > Not quite, the current package version is 24.35.30872.25, while the first > runtime release that dropped legacy support runtime is 24.35.30872.22. The runtime stopped working after the update, so it is definitely the 'non-legacy' version.
(In reply to Ivan Podmazov from comment #5) > Not quite, the current package version is 24.35.30872.25, while the first > runtime release that dropped legacy support runtime is 24.35.30872.22. thats why I talked about 'branch' ;-) 24.35 according to website. (In reply to Ivan Podmazov from comment #6) > (In reply to Ivan Podmazov from comment #5) > > Not quite, the current package version is 24.35.30872.25, while the first > > runtime release that dropped legacy support runtime is 24.35.30872.22. > > The runtime stopped working after the update, so it is definitely the > 'non-legacy' version. Thats strange. Upstream says: In case of critical fixes we plan to deliver them through a new release from 24.35 release branch. We have 24.35 branch, so you are sure?
(In reply to Conrad Kostecki from comment #7) > thats why I talked about 'branch' ;-) 24.35 according to website. > We have 24.35 branch, so you are sure? You're right, the branch is indeed 24.35. I believe that they meant that the legacy support will be based on this branch. Probably there are some patches or something that are applied to make deb packages with 'legacy1' suffix. But I can say for sure that the current ebuild downloads the latest runtime, not the legacy one.
(In reply to Ivan Podmazov from comment #8) > But I can say for sure that the current ebuild downloads the latest runtime, > not the legacy one. By the latest runtime I mean the one that does not support Gen8-Gen11 anymore.
They write: > If you are using legacy platform, follow latest 24.35 release procedure > instead the one below. More details in known issues section. > Support for Gen8, Gen9 and Gen11 devices will be delivered via packages with legacy1 suffix: > - intel-opencl-icd-legacy1_24.35.30872.22_amd64.deb > - intel-level-zero-gpu-legacy1_1.3.30872.22_amd64.deb I think the legacy runtime can be installed from a deb package only, not by building the 24.35 branch.
