public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/98340] gcc trunk build with clang failure, part 2 Date: Thu, 17 Dec 2020 17:52:38 +0000 [thread overview] Message-ID: <bug-98340-4-WHavKUaIJ9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98340-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98340 --- Comment #6 from Nathan Sidwell <nathan at gcc dot gnu.org> --- Now I look carefully, it appears to be trying to compile libiberty.a (the library) as a source file. Of course that'll barf. Configured using "CXX='clang -x c++ -std=c++11' CC=clang" (Of course I didn't look for any instructions :)
next prev parent reply other threads:[~2020-12-17 17:52 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-17 8:10 [Bug bootstrap/98340] New: " dcb314 at hotmail dot com 2020-12-17 8:18 ` [Bug bootstrap/98340] " dcb314 at hotmail dot com 2020-12-17 8:29 ` jakub at gcc dot gnu.org 2020-12-17 8:45 ` jakub at gcc dot gnu.org 2020-12-17 13:21 ` nathan at gcc dot gnu.org 2020-12-17 16:25 ` nathan at gcc dot gnu.org 2020-12-17 17:25 ` dcb314 at hotmail dot com 2020-12-17 17:52 ` nathan at gcc dot gnu.org [this message] 2020-12-17 17:57 ` cvs-commit at gcc dot gnu.org 2020-12-17 17:58 ` nathan 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-98340-4-WHavKUaIJ9@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).