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 bootstrap/106779] GCC 12.2 fails to compile in libiberty - uknown symbol PTR - requires later patch
Date: Tue, 30 Aug 2022 18:10:21 +0000	[thread overview]
Message-ID: <bug-106779-4-to6aeKAtdJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106779-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Where does the:
-I/tools/arch/Linux_3.10.0-x86_64/gcc-12.1.0-bootstrap//include
come there?  If it e.g. contains glibc fixincluded ansidecl.h, then that could
explain why it breaks.
But you don't want to use your build compiler's include directories in
preference over the build tree ones.

  parent reply	other threads:[~2022-08-30 18:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 16:30 [Bug bootstrap/106779] New: " todd_richmond at hotmail dot com
2022-08-30 16:33 ` [Bug bootstrap/106779] " todd_richmond at hotmail dot com
2022-08-30 17:12 ` jakub at gcc dot gnu.org
2022-08-30 17:59 ` todd_richmond at hotmail dot com
2022-08-30 18:00 ` todd_richmond at hotmail dot com
2022-08-30 18:04 ` jakub at gcc dot gnu.org
2022-08-30 18:10 ` jakub at gcc dot gnu.org [this message]
2022-08-30 19:07 ` todd_richmond at hotmail dot com
2022-08-30 23:42 ` egallager at gcc dot gnu.org
2022-08-31  7:48 ` jakub 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-106779-4-to6aeKAtdJ@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).