public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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, 06 May 2023 16:59:27 +0000	[thread overview]
Message-ID: <bug-109522-4-dZYhk1hUvp@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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Xi Ruoyao <xry111@gcc.gnu.org>:

https://gcc.gnu.org/g:be6c13d5cef6fd9ca97dea7a6f5fbf93c51235b5

commit r14-544-gbe6c13d5cef6fd9ca97dea7a6f5fbf93c51235b5
Author: Xi Ruoyao <xry111@xry111.site>
Date:   Sat Apr 15 19:55:50 2023 +0800

    build: Use -nostdinc generating macro_list [PR109522]

    This prevents a spurious message building a cross-compiler when target
    libc is not installed yet:

        cc1: error: no include path in which to search for stdc-predef.h

    As stdc-predef.h was added to define __STDC_* macros by libc, it's
    unlikely the header will ever contain some bad definitions w/o "__"
    prefix so it should be safe.

    gcc/ChangeLog:

            PR other/109522
            * Makefile.in (s-macro_list): Pass -nostdinc to
            $(GCC_FOR_TARGET).

  parent reply	other threads:[~2023-05-06 16:59 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 ` [Bug other/109522] " jakub at gcc dot gnu.org
2023-04-15 11:45 ` 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 [this message]
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-dZYhk1hUvp@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: link
Be 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).