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 bootstrap/104566] Internal compiler error in fail_formatted while building gcc from source while building GCC 11.2.0 with ubuntu's 7.5.0-3ubuntu1~18.04 Date: Wed, 16 Feb 2022 23:25:33 +0000 [thread overview] Message-ID: <bug-104566-4-VlNqLZVWR6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104566-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104566 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Internal compiler error in |Internal compiler error in |fail_formatted while |fail_formatted while |building gcc from source |building gcc from source | |while building GCC 11.2.0 | |with ubuntu's | |7.5.0-3ubuntu1~18.04 Version|11.2.0 |7.5.0 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Hmm, Makefile:4779: recipe for target 'all-stage1-gcc' failed Since this is stage 1 that is failing, the bug is related to the pre-installed compiler and not really GCC 11 issue. Also can you provide the output of "env"? Maybe there is a locale set which is causing this failure.
next prev parent reply other threads:[~2022-02-16 23:25 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-16 13:11 [Bug driver/104566] New: Internal compiler error while building from source xanderlenstra at gmail dot com 2022-02-16 23:25 ` pinskia at gcc dot gnu.org [this message] 2022-02-17 13:08 ` [Bug bootstrap/104566] Internal compiler error in fail_formatted while building gcc from source while building GCC 11.2.0 with ubuntu's 7.5.0-3ubuntu1~18.04 xanderlenstra at gmail dot com 2022-02-18 1:07 ` pinskia 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-104566-4-VlNqLZVWR6@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).