Hi Julien, On Tue, Apr 15, 2025 at 08:18:49PM +0200, Julien Nabet <[email protected]> wrote: > Ok it seems the pb is due to the fact I use --enable-python=fully-internal > > so I should find a way to add the module mesonbuild in the Python build.
I ran into the same error message with the following setup: 1) opensuse stable invokes python 3.6 via python3. 2) the meson package installs a meson script into /usr/bin that invokes python3.11 3) So running "meson" is OK, but our build system invokes "python3 meson", which is not OK. There has been advice on IRC that the "python3" prefix here is not wanted: 12:10 <ztrawhcse> vmiklos, cloph: if you're running "meson from PATH" then definitely do not prefix it with a python command as it could be absolutely anything 12:10 <ztrawhcse> could even be a C program 12:11 <ztrawhcse> "meson" could be the PyInstaller bootstrap extractor that is used to distribute standalone "looks like a C program" python redistributables 12:13 <ztrawhcse> if $MESON has been set to a non-PATH file containing a .py then that is a certain indicator it needs to run with a specific python 12:13 <ztrawhcse> (but note that it uses #!/usr/bin/env python3, so will find one on PATH if you inject python3 into PATH) Anyhow, the workaround I used is to install meson 0.61.5 into ~/bin, then "python3 meson" will work fine and the problem is avoided. It seems you hit a similar case because the internal python is Python-3.11.12, so in case your meson is not installed using that python, the python module of meson (mesonbuild) won't be found. I hope this helps. Regards, Miklos
