Good morning Ben, On 21.03.23 at 20:24 Ben Greiner wrote:
Am 21.03.23 um 17:05 schrieb Johannes Kastl:
It still complained, although /usr/bin/python3.10 was existing. I guess it is looking for something called "python3".
subunit or ansible-builder?
subunit.
So I also added python3-base. Which made the configure happy, but that somehow feels wrong. I want to avoid that somehow python3.6 is being used for building this package.
What would be the proper way? Patch the configure step to accept the python3.10 executable?
Decent configuration systems have a way to provide the path to the python executable and libraries/headers (from python3X-devel). Sometimes it is enough to provide PYTHON=/usr/bin/python3.10 or similar. If that is not the case yet, consider adding a patch and submit it upstream.
OK, I'll have a look, thanks. 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