public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102250] New: [11/12 Regression] python is not documented as a Prerequisite for building for riscv Date: Thu, 09 Sep 2021 04:44:26 +0000 [thread overview] Message-ID: <bug-102250-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102250 Bug ID: 102250 Summary: [11/12 Regression] python is not documented as a Prerequisite for building for riscv Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: documentation Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- Target: riscv The requirement for having python install is not documented to build for riscv-linux-gnu: https://gcc.gnu.org/install/prerequisites.html
next reply other threads:[~2021-09-09 4:44 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-09 4:44 pinskia at gcc dot gnu.org [this message] 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 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@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).