public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/43073] libiberty fails to build when using gcc-core Date: Mon, 19 Jul 2021 13:10:30 +0000 [thread overview] Message-ID: <bug-43073-4-7cEDUUAP3W@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-43073-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43073 --- Comment #8 from Segher Boessenkool <segher at gcc dot gnu.org> --- Much more importantly, gcc-core doesn't exist anymore (so WORKSFORME is a strange resolution). Using the documented build procedures is recommended, and is what is supported here (not any cross tool whatever thing).
next prev parent reply other threads:[~2021-07-19 13:10 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-43073-4@http.gcc.gnu.org/bugzilla/> 2011-02-06 7:22 ` laguest at archeia dot com 2021-07-19 6:04 ` pinskia at gcc dot gnu.org 2021-07-19 13:10 ` segher at gcc dot gnu.org [this message] 2010-02-15 9:24 [Bug c/43073] New: building arm cross-compiler fails when attempting to build regex library eric at brouhaha dot com 2010-06-07 14:36 ` [Bug bootstrap/43073] libiberty fails to build when using gcc-core zero at boolean-domain dot net
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-43073-4-7cEDUUAP3W@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).