qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] scripts: make sure scripts are invoked via $(PYTHON)
Date: Thu, 18 May 2023 06:19:46 -0700	[thread overview]
Message-ID: <146ff261-3367-e844-cfc2-822ee0d1d6e5@linaro.org> (raw)
In-Reply-To: <20230518113355.1006000-1-pbonzini@redhat.com>

On 5/18/23 04:33, Paolo Bonzini wrote:
> Some scripts are invoked via the first "python3" binary in the PATH,
> because they are executable and their shebang line is "#! /usr/bin/env
> python3".  To enforce usage of $(PYTHON), make them nonexecutable.
> Scripts invoked via meson need nothing else, and meson-buildoptions.py
> is already using $(PYTHON).  For probe-gdb-support.py however the
> invocation in the configure script has to be adjusted.
> 
> Signed-off-by: Paolo Bonzini<pbonzini@redhat.com>
> ---
>   configure                     | 2 +-
>   scripts/meson-buildoptions.py | 0
>   scripts/modinfo-collect.py    | 0
>   scripts/modinfo-generate.py   | 0
>   scripts/probe-gdb-support.py  | 0
>   5 files changed, 1 insertion(+), 1 deletion(-)
>   mode change 100755 => 100644 scripts/meson-buildoptions.py
>   mode change 100755 => 100644 scripts/modinfo-collect.py
>   mode change 100755 => 100644 scripts/modinfo-generate.py
>   mode change 100755 => 100644 scripts/probe-gdb-support.py

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>

r~


      reply	other threads:[~2023-05-18 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 11:33 [PATCH] scripts: make sure scripts are invoked via $(PYTHON) Paolo Bonzini
2023-05-18 13:19 ` Richard Henderson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=146ff261-3367-e844-cfc2-822ee0d1d6e5@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).