public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "todd_richmond at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/106779] New: GCC 12.2 fails to compile in libiberty - uknown symbol PTR - requires later patch
Date: Tue, 30 Aug 2022 16:30:41 +0000	[thread overview]
Message-ID: <bug-106779-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106779
           Summary: GCC 12.2 fails to compile in libiberty - uknown symbol
                    PTR - requires later patch
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: todd_richmond at hotmail dot com
  Target Milestone: ---

I have been able to build every gcc release from 8 to 12.2 on both CentOS6 and
CentOS 7 w/o problem including 12.1. However, 12.2 fails to compile
libiberty/objdump.c due to "PTR" not being defined. I tried compiling with
10.2, 11.3 and 12.1 w/o success

However, a big change was recently checked into libiberty that eliminates the
PTR macro, but 12.2 does not include it. I can confirm that this diff works
correctly

https://github.com/gcc-mirror/gcc/commit/50b009c5daef92bc60fc26fcc4c495e117667387.patch

             reply	other threads:[~2022-08-30 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 16:30 todd_richmond at hotmail dot com [this message]
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
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@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).