From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: mark.kettenis@xs4all.nl, gdb-patches@sourceware.org
Subject: Re: [patch] Fix warnings using gcc-4.5 HEAD
Date: Sat, 11 Jul 2009 12:09:00 -0000 [thread overview]
Message-ID: <837hyfy3fv.fsf@gnu.org> (raw)
In-Reply-To: <20090711083928.GA30826@host0.dyn.jankratochvil.net>
> Date: Sat, 11 Jul 2009 10:39:28 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org
>
> There is no way how to extend 3rd party enum X definition:
> error: nested redefinition of ‘enum X’
> error: redeclaration of ‘enum X’
Aren't there ways of cleaning this up other than extending existing
enum definitions?
next prev parent reply other threads:[~2009-07-11 9:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 8:39 Jan Kratochvil
2009-07-11 8:46 ` Mark Kettenis
2009-07-11 9:25 ` Jan Kratochvil
2009-07-11 12:09 ` Eli Zaretskii [this message]
2009-07-11 19:02 ` Jan Kratochvil
2009-07-30 0:28 ` Tom Tromey
2009-09-08 18:52 ` Jan Kratochvil
2009-09-10 1:48 ` Joel Brobecker
2009-09-10 7:29 ` Jan Kratochvil
2009-09-15 16:11 ` Jan Kratochvil
2009-07-11 9:32 ` Eli Zaretskii
2009-07-11 20:58 ` Daniel Jacobowitz
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=837hyfy3fv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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