Installation of the system package readline-devel solved the problem. Now
sage-10.1 and sage-10.2.rc4 compile and run on my tumbleweed without
problems. Maybe, this package is contained in the "standard" tumbleweed
configuration but not in the "minimal" one. It is strange though that it
used
Our CI tests with the official opensuse/tumbleweed Docker image,
see https://github.com/sagemath/sage/blob/develop/tox.ini#L381
I think it's updated daily.
On Monday, November 20, 2023 at 2:39:54 PM UTC-8 Christian Bär wrote:
> How recent is the tumbleweed install you are testing against? As
>
How recent is the tumbleweed install you are testing against? As mentioned,
sage-10.1 initially did compile until some tumbleweed update broke it,
leading to the error message described above. This is why I am skeptical
that installing more system packages will resolve the problem.
Matthias
For reference, this
is https://github.com/sagemath/sage/issues/27750#issuecomment-1432504494
(the easy fix somehow never made it into Sage)
It will go away in our upgrade to FLINT 3,
https://github.com/sagemath/sage/pull/35848, which does not have these
problematic LD_LIBRARY_PATH
We also see this failure on opensuse-tumbleweed in our CI in the "minimal"
system package
configuration
https://github.com/sagemath/sage/actions/runs/6909825582/job/18801882455#step:11:2323
However, the "standard" system package configuration builds and tests
fine: