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/97481] GCC ice when build with RISCV on msys2 Date: Mon, 19 Oct 2020 19:27:28 +0000 [thread overview] Message-ID: <bug-97481-4-lJmAp5kwS8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97481-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97481 Jim Wilson <wilson at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wilson at gcc dot gnu.org --- Comment #2 from Jim Wilson <wilson at gcc dot gnu.org> --- riscv-unknown-linux-gnu is not a supported target. You must use either riscv32-unknown-linux-gnu or riscv64-unknwon-linux-gnu. Both compilers support both word sizes, the only difference is which is the default word size. This may be part of the reason why it failed. The attachment doesn't show any ICE. It is just a config.log file, and I don't see anything interesting in there. Note that mingw64 builds of a linux toolchain are unlikely to work as glibc requires a case sensitive file system. I'd suggest using WSL2 as something more likely to work, but I haven't tried that myself. It looks like you have a badly broken compiler build. You will need to figure out why it is broken. This doesn't seem to be a gcc problem, but rather a build problem on your side.
next prev parent reply other threads:[~2020-10-19 19:27 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-18 21:06 [Bug bootstrap/97481] New: " euloanty at live dot com 2020-10-18 21:08 ` [Bug bootstrap/97481] " euloanty at live dot com 2020-10-19 19:27 ` wilson at gcc dot gnu.org [this message] 2020-10-19 20:54 ` [Bug target/97481] " euloanty at live dot com 2020-10-19 21:28 ` euloanty at live dot com 2020-10-19 22:13 ` euloanty at live dot com
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-97481-4-lJmAp5kwS8@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).