public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ahajkova at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28444] New: gdb fails to build on ppc64le when building with -flto
Date: Mon, 11 Oct 2021 20:24:37 +0000	[thread overview]
Message-ID: <bug-28444-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=28444

            Bug ID: 28444
           Summary: gdb fails to build on ppc64le when building with -flto
           Product: gdb
           Version: 11.2
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: ahajkova at redhat dot com
  Target Milestone: ---

gcc-11.2.1-1.fc35.ppc64le
gdb-10.2-6.fc35.ppc64le
Fedora-Rawhide

clone gdb and build it as follows

1.flags="-g3 -Og -flto" CFLAGS="$flags" CXXFLAGS="$flags"
../binutils-gdb/configure --disable-binutils --disable-elfcpp --disable-gas
--disable-gold --disable-gprof --disable-ld  --enable-unit-tests
--with-system-readline --with-separate-debug-dir=/usr --disable-sim
2.make -j `nproc`

results:
../../binutils-gdb/gdbserver/../gdb/arch/ppc-linux-tdesc.h:44:28: error:
‘tdesc_powerpc_isa207_htm_vsx64l’ violates the C++ One Definition Rule
[-Werror=odr]
   44 | extern struct target_desc *tdesc_powerpc_isa207_htm_vsx64l;


Note:
struct target_desc is actually defined in gdb/target-descriptions.c. Not in a
header.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-10-11 20:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 20:24 ahajkova at redhat dot com [this message]
2022-03-06 17:10 ` [Bug gdb/28444] " tromey at sourceware dot org
2023-09-11  7:35 ` vries 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-28444-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).