public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/109522] Spurious "cc1: error: no include path in which to search for stdc-predef.h" building a cross compiler Date: Sat, 15 Apr 2023 07:53:41 +0000 [thread overview] Message-ID: <bug-109522-4-dwjNvy4NyF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109522-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109522 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I bet we really don't need the macros from stdc-predef.h, so perhaps we could use -nostdinc. stdc-predef.h currently (sometimes) predefines __STDC_IEC_559__ __STDC_IEC_60559_BFP__ __STDC_IEC_559_COMPLEX__ __STDC_IEC_60559_COMPLEX__ __STDC_ISO_10646__ and grep doesn't find any STDC_IEC nor STDC_ISO occurrences in fixincl.
next prev parent reply other threads:[~2023-04-15 7:53 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-15 7:42 [Bug other/109522] New: " xry111 at gcc dot gnu.org 2023-04-15 7:53 ` jakub at gcc dot gnu.org [this message] 2023-04-15 11:45 ` [Bug other/109522] " xry111 at gcc dot gnu.org 2023-04-15 12:02 ` xry111 at gcc dot gnu.org 2023-05-06 16:59 ` cvs-commit at gcc dot gnu.org 2023-05-06 17:01 ` xry111 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-109522-4-dwjNvy4NyF@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).