Hello Stephan,
Just for information, it worked perfectly, thank you!
Now I also read Christian's feedback in this thread and know there'll be
another solution but, at least, I'm not stuck anymore.
Julien
Hi *,
On Wed, Apr 16, 2025 at 9:21 AM Stephan Bergmann
wrote:
>
> On 16.04.25 08:40, Stephan Bergmann wrote:
> > On 16.04.25 08:15, Miklos Vajna wrote:
> >> There has been advice on IRC that the "python3" prefix here is not
> >> wanted:
> >> […]
> >> It seems you hit a similar case because the in
On 16.04.25 08:40, Stephan Bergmann wrote:
On 16.04.25 08:15, Miklos Vajna wrote:
There has been advice on IRC that the "python3" prefix here is not
wanted:
12:10 vmiklos, cloph: if you're running "meson from PATH"
then definitely do not prefix it with a python command as it could be
absolut
On 16.04.25 08:15, Miklos Vajna wrote:
There has been advice on IRC that the "python3" prefix here is not
wanted:
12:10 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 could even be a C program
Hi Julien,
On Tue, Apr 15, 2025 at 08:18:49PM +0200, Julien Nabet
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) ope
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.
