Thanks. Does it help to add a compatibily link?

  sudo ln -s /usr/share/clc /usr/lib64/clc

Yes, it helps. clinfo and clpeak works as expected.

Thanks. Should be fixed now.

https://build.opensuse.org/request/show/931436

Looks like this got broken with

-------------------------------------------------------------------
Fri Oct 30 15:33:35 UTC 2020 - Aaron Puchert <aaronpuchert@alice-dsl.net>

- Update to version 0.2.0+llvm11.0.0.
[...]
- The library files have moved from %{_libdir} to %{_datadir}.
- Make noarch: the bitcode files don't depend on the host CPU.

So since more than a year ...

Could you please also make maintenance update for Leap 15.3?

libclc on Leap 15.3 is not affected by this issue.

No, it is. I am facing this issue on Leap 15.3 right now.

I don't understand this. Latest changelog on Leap 15.3 is

Fri Oct 12 01:55:46 UTC 2018 - jimmy@boombatower.com

- Update to version 0.2.0+git.20180915:

Also there /usr/lib64/clc is still being used.

%files
[...]
%{_libdir}/clc

Maybe you're using packages from X11:XOrg project? But this is now fixed. It's the devel project for Factory/Tumbleweed.

I use the package provided by the distro:

> rpm -q -f /usr/share/clc/polaris11-amdgcn-mesa-mesa3d.bc --info
Name        : libclc
Version     : 0.2.0+llvm11.0.1
Release     : bp153.1.2
Architecture: noarch
Install Date: Вс 14 ноя 2021 16:33:19
Group       : Development/Libraries/C and C++
Size        : 74525857
License     : (BSD-3-Clause OR MIT) AND Apache-2.0 WITH LLVM-exception
Signature   : RSA/SHA256, Чт 22 апр 2021 11:34:18, Key ID 9c214d4065176565
Source RPM  : libclc-0.2.0+llvm11.0.1-bp153.1.2.src.rpm
Build Date  : Чт 22 апр 2021 11:33:23
Build Host  : old-atreju3
Relocations : (not relocatable)
Packager    : https://bugs.opensuse.org
Vendor      : openSUSE
URL         : https://libclc.llvm.org/
Summary     : OpenCL C programming language library
Description :
Library requirements of the OpenCL C programming language.
Distribution: SUSE Linux Enterprise 15 SP3



> rpm -q -f /usr/share/clc/polaris11-amdgcn-mesa-mesa3d.bc --changes | head
* Сб 09 янв 2021 15:00:00 Aaron Puchert <aaronpuchert@alice-dsl.net>
- Update to version 0.2.0+llvm11.0.1.

* Пт 30 окт 2020 15:00:00 Aaron Puchert <aaronpuchert@alice-dsl.net>
- Update to version 0.2.0+llvm11.0.0.
  The repository that we extracted the tarball from isn't updated
  any longer. So we take the tarballs from LLVM releases instead.
- The build now uses CMake instead of a custom Python script.
- Remove dependencies on gcc, libstdc++-devel, ncurses and zlib.
- The provided package consists of LLVM bitcode files, which are

https://download.opensuse.org/distribution/leap/15.3/repo/oss/noarch/libclc-0.2.0+llvm11.0.1-bp153.1.2.noarch.rpm

This is weird. Indeed libclc has been updated for Leap 15.3, but not for SLE15-SP3. This should not happen. Not sure why this has been accepted ...

done

https://build.opensuse.org/request/show/931442

(In reply to Stefan Dirsch from comment #3)
> Looks like this got broken with
> 
> -------------------------------------------------------------------
> Fri Oct 30 15:33:35 UTC 2020 - Aaron Puchert <aaronpuchert@alice-dsl.net>
> 
> - Update to version 0.2.0+llvm11.0.0.
> [...]
> - The library files have moved from %{_libdir} to %{_datadir}.
> - Make noarch: the bitcode files don't depend on the host CPU.
> 
> So since more than a year ...

Nothing broken on Tumbleweed for me. The files moved, but that is reflected in the pkgconfig:

$ cat /usr/share/pkgconfig/libclc.pc
includedir=/usr/include
libexecdir=/usr/share/clc

Name: libclc
Description: Library requirements of the OpenCL C programming language
Version: 0.2.0
Cflags: -I${includedir}
Libs: -L${libexecdir}

Mesa picks that up just fine. The problem is probably that Leap's Mesa was still compiled with the older libclc in SLE.

(In reply to Stefan Dirsch from comment #10)
> This is weird. Indeed libclc has been updated for Leap 15.3, but not for
> SLE15-SP3. This should not happen. Not sure why this has been accepted ...
The package was in Backports before I submitted the update. [1] But you're right, I should have tried to get this into SLE, not sure why I didn't consider that. There were some discussions about updating the llvm metapackage in SLE which didn't happen, and so I had to create some overlay packages in Leap to avert version downgrades in Leap 15.3 versus 15.2 (bug 1184920).

Though I don't see a reason to not update libclc, after all Mesa was also starting to use llvm11.

[1] https://build.opensuse.org/package/revisions/openSUSE:Backports:SLE-15-SP3/libclc

Thanks. Understood. I reverted the SR against Factory/Tumbleweed. Mesa should have been rebiult and released as well with the libclc update in Leap 15.3.  Since you're not working at SUSE you cannot submit anything against SLE.  At least we didn't break it there as well. that way;-)

I've just reopened this issue in order not to lost it in the history.

I made a Submit request for Leap 15.3. So once this has been checked in and the update released, things are fixed. If there are issue with the SR and things cannot be fixed as I planned I'll reopen the bugreport.

I can't do more than this. I need to close my bugs once they are addressed from my point. Otherwise I lose any overview over my bugs.

(In reply to Matwey Kornilov from comment #15)
> I've just reopened this issue in order not to lost it in the history.
I guess we can't do anything further in the SP3 codeline, but we could try to fix it for SP4. (That is, update libclc in SLE and drop it from Backports.)

I'd suggest to file a new report against Leap 15.4.

libclc and Mesa has been updated for SP4 to current Tumbleweed version and everything will be freshly built. So in SP4 we're fine.

(In reply to Stefan Dirsch from comment #18)
> libclc and Mesa has been updated for SP4 to current Tumbleweed version and
> everything will be freshly built. So in SP4 we're fine.
Should we also delete https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP4/libclc then so that SLE and Leap share the same package?

I don't know the meaning of these Backports repos. It's the first time I see these. But yes, we want to have the same package on sle15-sp4 and Leap 15.4!

(In reply to Stefan Dirsch from comment #20)
> I don't know the meaning of these Backports repos. It's the first time I see
> these. But yes, we want to have the same package on sle15-sp4 and Leap 15.4!
These are basically the packages that Leap has on top of SLE. Normally they should not have any packages in common, but some overlay packages are there.

We should probably file a delete request for that.

(In reply to Aaron Puchert from comment #21)
> (In reply to Stefan Dirsch from comment #20)
> > I don't know the meaning of these Backports repos. It's the first time I see
> > these. But yes, we want to have the same package on sle15-sp4 and Leap 15.4!
> These are basically the packages that Leap has on top of SLE. Normally they
> should not have any packages in common, but some overlay packages are there.
> 
> We should probably file a delete request for that.

Yes. Please go ahead!

Filed delete request https://build.opensuse.org/request/show/931639.

(In reply to Aaron Puchert from comment #23)
> Filed delete request https://build.opensuse.org/request/show/931639.

Thanks!

openSUSE-RU-2021:1499-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 1192675
CVE References: 
JIRA References: 
Sources used:
openSUSE Backports SLE-15-SP3 (src):    libclc-0.2.0+llvm11.0.1-bp153.2.3.1