public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kito at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98152] [11 regression] /usr/bin/env: 'python': No such file or directory Date: Sun, 06 Dec 2020 03:29:57 +0000 [thread overview] Message-ID: <bug-98152-4-sPOFhMnzPC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98152-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98152 Kito Cheng <kito at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |kito at gcc dot gnu.org --- Comment #2 from Kito Cheng <kito at gcc dot gnu.org> --- The script has test with python2 and python3, but seems like require python as essential for building RISC-V is inappropriate, I'll send patch later to made this become optional.
next prev parent reply other threads:[~2020-12-06 3:29 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-05 8:26 [Bug target/98152] New: " schwab@linux-m68k.org 2020-12-05 8:27 ` [Bug target/98152] " schwab@linux-m68k.org 2020-12-05 16:06 ` marxin at gcc dot gnu.org 2020-12-06 3:29 ` kito at gcc dot gnu.org [this message] 2020-12-07 7:51 ` rguenth at gcc dot gnu.org 2020-12-08 7:52 ` cvs-commit at gcc dot gnu.org 2020-12-08 7:57 ` kito at gcc dot gnu.org
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-98152-4-sPOFhMnzPC@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: linkBe 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).