* dectree.py uses env python3 rather than configured python
@ 2021-04-06 18:50 Dr. David Alan Gilbert
2021-04-06 19:38 ` John Snow
0 siblings, 1 reply; 4+ messages in thread
From: Dr. David Alan Gilbert @ 2021-04-06 18:50 UTC (permalink / raw)
To: tsimpson, jsnow; +Cc: qemu-devel
Hi Taylor,
I tripped over dectree.py using 'env python3'; the qemu configure
script lets you specify a python with e.g.:
--with-python=/usr/libexec/platform-python
and I think everywhere else in qemu uses the configured python.
(This host, like most standard rhel8, doesn't have a python3 binary out
of the box)
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: dectree.py uses env python3 rather than configured python
2021-04-06 18:50 dectree.py uses env python3 rather than configured python Dr. David Alan Gilbert
@ 2021-04-06 19:38 ` John Snow
2021-04-06 19:47 ` Taylor Simpson
0 siblings, 1 reply; 4+ messages in thread
From: John Snow @ 2021-04-06 19:38 UTC (permalink / raw)
To: Dr. David Alan Gilbert, tsimpson; +Cc: qemu-devel
On 4/6/21 2:50 PM, Dr. David Alan Gilbert wrote:
> Hi Taylor,
> I tripped over dectree.py using 'env python3'; the qemu configure
> script lets you specify a python with e.g.:
> --with-python=/usr/libexec/platform-python
>
> and I think everywhere else in qemu uses the configured python.
> (This host, like most standard rhel8, doesn't have a python3 binary out
> of the box)
>
> Dave
>
Hi,
Instead of allowing meson to invoke this script directly (and have the
shebang be processed by the shell), meson ought to be taught to invoke
it directly using the user's configured python interpreter.
The shebang "#!/usr/bin/env python3" is otherwise the correct one to
use, and should (probably) be left alone.
--js
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: dectree.py uses env python3 rather than configured python
2021-04-06 19:38 ` John Snow
@ 2021-04-06 19:47 ` Taylor Simpson
2021-04-06 20:13 ` Peter Maydell
0 siblings, 1 reply; 4+ messages in thread
From: Taylor Simpson @ 2021-04-06 19:47 UTC (permalink / raw)
To: John Snow, Dr. David Alan Gilbert; +Cc: qemu-devel
> -----Original Message-----
> From: John Snow <jsnow@redhat.com>
> Sent: Tuesday, April 6, 2021 2:38 PM
> To: Dr. David Alan Gilbert <dgilbert@redhat.com>; Taylor Simpson
> <tsimpson@quicinc.com>
> Cc: qemu-devel@nongnu.org
> Subject: Re: dectree.py uses env python3 rather than configured python
>
> On 4/6/21 2:50 PM, Dr. David Alan Gilbert wrote:
> > Hi Taylor,
> > I tripped over dectree.py using 'env python3'; the qemu configure
> > script lets you specify a python with e.g.:
> > --with-python=/usr/libexec/platform-python
> >
> > and I think everywhere else in qemu uses the configured python.
> > (This host, like most standard rhel8, doesn't have a python3 binary out
> > of the box)
> >
> > Dave
> >
>
> Hi,
>
> Instead of allowing meson to invoke this script directly (and have the
> shebang be processed by the shell), meson ought to be taught to invoke
> it directly using the user's configured python interpreter.
>
> The shebang "#!/usr/bin/env python3" is otherwise the correct one to
> use, and should (probably) be left alone.
>
> --js
Yes, I think meson.build would be the right place to change the behavior.
On the other hand, isn't python3 standard for building qemu now? This page
https://wiki.qemu.org/Hosts/Linux#Required_additional_packages
lists python3 as an additional required package for RHEL8.
Thanks,
Taylor
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-04-06 20:14 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-06 18:50 dectree.py uses env python3 rather than configured python Dr. David Alan Gilbert
2021-04-06 19:38 ` John Snow
2021-04-06 19:47 ` Taylor Simpson
2021-04-06 20:13 ` Peter Maydell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).