Hi Ben, On 24.03.23 at 10:22 Ben Greiner wrote:
Am 24.03.23 um 07:07 schrieb Johannes Kastl:
The best I could come up with was using export PYTHON=/usr/bin/python%{python_version}
Don't do this. You never really know what the flavor-agnostic %python_version might be by default.
If you have just python310, nothing else: export PYTHON=%__python310
If you iterate of multiple flavors in %pythons: %{python_expand # iterate over all flavors in buildset. Special macro handling of "$python"! # $python is python3.10 here export PYTHON=$(command -v $python) # $python is python310 here export PYTHON=%{__$python} # Do your configure and build steps inside the expand make }
I am not sure what is needed for subunit. It is not a pure python package, but has python subpackages:
https://build.opensuse.org/project/show/home:ojkastl_buildservice:branches:d...
To me it looked like the configure only runs once. And apparently it picks python3 on Tumbleweed, so I daresay it is enough that it finds a python, but it does not fail if it is "the wrong one".
%configure \ --enable-shared \ --disable-static
%make_build %pyproject_wheel
I will gladly rework the SR, no problem. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537