public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/109668] 'python' vs. 'python3'
Date: Fri, 15 Mar 2024 23:29:27 +0000 [thread overview]
Message-ID: <bug-109668-4-2ue61Qbth4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109668-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109668
--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:8c4785e77e8b54109fbb4f81a3b624e98184c2aa
commit r13-8449-g8c4785e77e8b54109fbb4f81a3b624e98184c2aa
Author: Sam James <sam@gentoo.org>
Date: Fri Mar 8 15:24:20 2024 +0100
contrib: Improve dg-extract-results.sh's Python detection [PR109668]
'python' on some systems (e.g. SLES 15) might be Python 2. Prefer python3,
then python, then python2 (as the script still tries to work there).
PR other/109668
* dg-extract-results.sh: Check for python3 before python. Check for
python2 last.
(cherry picked from commit 64273a7e6bd8ba60058174d147521dd65d705637)
prev parent reply other threads:[~2024-03-15 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 12:35 [Bug other/109668] New: " tschwinge at gcc dot gnu.org
2023-05-09 11:41 ` [Bug other/109668] " marxin at gcc dot gnu.org
2023-10-24 7:46 ` piannetta at kalrayinc dot com
2024-02-09 16:55 ` palmer at gcc dot gnu.org
2024-02-23 4:36 ` cvs-commit at gcc dot gnu.org
2024-03-08 14:27 ` cvs-commit at gcc dot gnu.org
2024-03-15 23:29 ` cvs-commit at gcc dot gnu.org [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=bug-109668-4-2ue61Qbth4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).