public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102250] [11/12 Regression] python is not documented as a Prerequisite for building for riscv Date: Thu, 09 Sep 2021 19:11:18 +0000 [thread overview] Message-ID: <bug-102250-4-8O03b7eHNH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102250-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102250 Jim Wilson <wilson at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wilson at gcc dot gnu.org --- Comment #3 from Jim Wilson <wilson at gcc dot gnu.org> --- There is no python requirement for building a riscv linux compiler. It is only needed if the user specifies the optional --with-arch configure option, and if the user specifies a non-canonical form of the architecture string in the --with-arch option string. Otherwise gcc will build fine without python. A later patch fixed this to check for python before using it, after Andreas Schwab complained about this.
next prev parent reply other threads:[~2021-09-09 19:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-09 4:44 [Bug target/102250] New: " pinskia at gcc dot gnu.org 2021-09-09 4:44 ` [Bug target/102250] " pinskia at gcc dot gnu.org 2021-09-09 4:45 ` pinskia at gcc dot gnu.org 2021-09-09 5:18 ` pinskia at gcc dot gnu.org 2021-09-09 19:11 ` wilson at gcc dot gnu.org [this message] 2022-04-21 7:50 ` rguenth at gcc dot gnu.org 2022-07-26 13:29 ` [Bug target/102250] [11/12/13 " rguenth at gcc dot gnu.org 2023-05-29 10:05 ` [Bug target/102250] [11/12/13/14 " jakub at gcc dot gnu.org 2024-03-10 3:14 ` cvs-commit at gcc dot gnu.org 2024-05-13 11:37 ` [Bug target/102250] [11/12/13 " rguenth 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-102250-4-8O03b7eHNH@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).