On 16.10.24 18:29 Jan Engelhardt wrote:
On Wednesday 2024-10-16 18:13, Johannes Kastl wrote:
On 16.10.24 17:44 Jan Engelhardt wrote:
Seems pretty obvious that ABSL is not installed (BuildRequired) or that ABSL (if it is installed) is so old that it does not contain libabsl_log_internal_check_op.so yet.
Thanks for your answer. I can of course add this dependency.
My question remains: Why is this different between SLE15SP5 and Leap 15.5?
Usually: accidental inclusion through some other dependency. You can make a local build for Tumbleweed (`osc build`), then abort it midway, enter the chroot it had created (`osc chroot`) and then attempt to remove absl (rpm -qa 'libasbl*', rpm -e libabsl2024xyz), the latter of which will fail and tell how it came in.
Building against openSUSE:Leap-15.5, abseil-cpp-devel does not pull in libabsl2401_0_0. Building against openSUSE:Leap-15.5:Update, it does. And the build succeeds. On non-Update, the package does not even exist. So, even adding both abseil-cpp-devel and libabsl2401_0_0 to the packages does not solve this. Only building against openSUSE:Leap-15.6:Update. This really makes me wonder why adding Leap 15.5 from the project's repository section adds the non-Update project by default. I think adding Leap to a project as build target should use the Update project, not the non-Update one. Kind Regards, Johannes