From: Jeff Law <jeffreyalaw@gmail.com>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] build: Use -nostdinc generating macro_list [PR109522]
Date: Sat, 29 Apr 2023 12:05:08 -0600 [thread overview]
Message-ID: <b9d26adb-f5af-875d-0658-61dce9c7fd92@gmail.com> (raw)
In-Reply-To: <20230415120105.131576-1-xry111@xry111.site>
On 4/15/23 06:01, Xi Ruoyao via Gcc-patches wrote:
> 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).
OK. Thanks.
jeff
next prev parent reply other threads:[~2023-04-29 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 12:01 Xi Ruoyao
2023-04-29 18:05 ` Jeff Law [this message]
2023-05-06 17:01 ` Pushed: " Xi Ruoyao
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=b9d26adb-f5af-875d-0658-61dce9c7fd92@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=xry111@xry111.site \
/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).