public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/22395] ODR violations
Date: Mon, 14 Aug 2023 16:32:44 +0000 [thread overview]
Message-ID: <bug-22395-4717-HwTZmxUVnK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22395-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22395
--- Comment #16 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6a93ab8af49be41a44af1b4651e9ab2ebc6d2f77
commit 6a93ab8af49be41a44af1b4651e9ab2ebc6d2f77
Author: Tom de Vries <tdevries@suse.de>
Date: Mon Aug 14 18:32:29 2023 +0200
[gdb/build] Fix enum param_types odr violation
When building gdb with -O2 -flto, I run into:
...
gdb/guile/scm-param.c:121:6: warning: type 'param_types' violates the C++ \
One Definition Rule [-Wodr]
enum param_types
^
gdb/python/py-param.c:33:6: note: an enum with different value name is \
defined in another translation unit
enum param_types
^
...
Fix this by renaming to enum scm_param_types and py_param_types.
Tested on x86_64-linux.
Approved-By: Tom Tromey <tom@tromey.com>
PR build/22395
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=22395
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-14 16:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-22395-4717@http.sourceware.org/bugzilla/>
2021-01-09 17:18 ` tromey at sourceware dot org
2021-03-11 19:47 ` tromey at sourceware dot org
2021-03-12 17:03 ` cbiesinger at google dot com
2021-03-12 17:46 ` palves at redhat dot com
2021-03-12 18:29 ` tromey at sourceware dot org
2021-03-12 18:58 ` schwab@linux-m68k.org
2022-03-06 17:10 ` tromey at sourceware dot org
2022-03-06 17:11 ` tromey at sourceware dot org
2022-05-20 15:04 ` tromey at sourceware dot org
2022-06-02 15:30 ` tromey at sourceware dot org
2022-09-09 0:56 ` tromey at sourceware dot org
2022-11-08 11:01 ` ago at gentoo dot org
2022-11-10 22:09 ` tromey at sourceware dot org
2022-11-10 22:12 ` tromey at sourceware dot org
2022-11-11 5:30 ` sam at gentoo dot org
2023-08-14 9:30 ` vries at gcc dot gnu.org
2023-08-14 12:25 ` vries at gcc dot gnu.org
2023-08-14 12:36 ` tromey at sourceware dot org
2023-08-14 15:50 ` vries at gcc dot gnu.org
2023-08-14 16:32 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-14 16:32 ` cvs-commit at gcc dot gnu.org
2023-08-14 16:32 ` cvs-commit at gcc dot gnu.org
2023-08-14 20:53 ` cvs-commit at gcc dot gnu.org
2023-08-15 3:28 ` sam at gentoo dot org
2023-08-17 9:39 ` vries at gcc dot gnu.org
2023-08-17 15:10 ` cvs-commit at gcc dot gnu.org
2023-08-22 17:36 ` vries at gcc dot gnu.org
2023-09-11 6:55 ` vries at gcc dot gnu.org
2023-09-11 7:29 ` vries at gcc dot gnu.org
2023-09-11 20:02 ` sam at gentoo dot org
2023-09-27 7:36 ` sam at gentoo dot 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-22395-4717-HwTZmxUVnK@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).