public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/109522] New: Spurious "cc1: error: no include path in which to search for stdc-predef.h" building a cross compiler
Date: Sat, 15 Apr 2023 07:42:58 +0000	[thread overview]
Message-ID: <bug-109522-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109522

            Bug ID: 109522
           Summary: Spurious "cc1: error: no include path in which to
                    search for stdc-predef.h" building a cross compiler
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: xry111 at gcc dot gnu.org
  Target Milestone: ---

Build a cross compiler (with target libc not installed yet):

../gcc/configure --target=loongarch64-linux-gnu --disable-multilib
--with-system-zlib && make gcc

Then a spurious message is outputted for macro_list:

echo | /home/xry111/git-repos/gcc-la/./gcc/xgcc
-B/home/xry111/git-repos/gcc-la/./gcc/  -E -dM - | \
  sed -n -e 's/^#define \([^_][a-zA-Z0-9_]*\).*/\1/p' \
         -e 's/^#define \(_[^_A-Z][a-zA-Z0-9_]*\).*/\1/p' | \
  sort -u > tmp-macro_list
cc1: error: no include path in which to search for stdc-predef.h
/bin/sh ../../gcc/gcc/../move-if-change tmp-macro_list macro_list

Though the macro_list file is created successfully, the message can lead people
to think something is wrong.

             reply	other threads:[~2023-04-15  7:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-15  7:42 xry111 at gcc dot gnu.org [this message]
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
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@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).