From: Marcel Apfelbaum <marcel.a@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Andreas Färber" <afaerber@suse.de>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Anthony Liguori" <aliguori@amazon.com>,
"Brad Smith" <brad@comstyle.com>
Subject: Re: [Qemu-devel] [PATCH for-2.0] vl.c: Fix OpenBSD compilation issue due to namespace collisions
Date: Tue, 18 Mar 2014 16:42:18 +0200 [thread overview]
Message-ID: <1395153738.2328.11.camel@localhost.localdomain> (raw)
In-Reply-To: <CAFEAcA-upsA4YU-b5q0pJ98EMhKrq=oaxU2xOzSi2iJDxDJkVA@mail.gmail.com>
On Tue, 2014-03-18 at 14:28 +0000, Peter Maydell wrote:
> On 18 March 2014 14:27, Marcel Apfelbaum <marcel.a@redhat.com> wrote:
> > On Tue, 2014-03-18 at 16:05 +0200, Marcel Apfelbaum wrote:
> >> On Tue, 2014-03-18 at 13:57 +0000, Peter Maydell wrote:
> >> > I'm confused; why doesn't this just result in a compiler
> >> > error in the other direction when we try to #define
> >> > MACHINE in QEMU and it's already been defined by
> >> > the BSD headers?
> >> Maybe because there is usage of the "MACHINE" define by the BSD
> >> library? (on Qemu context, of course! - meaning, it shouldn't even be
> >> exposed in the first place!)
> > I meant "there is *no* usage of the..."
>
> But we'll still see
> #define MACHINE something
> and then later
> #define MACHINE something-else
>
> right? The compiler ought to complain about that, at point
> of the second #define; use or otherwise of the macro isn't
> relevant here.
Right! Sorry.
As Andreas said in IRC, BSDs do not build with -Werror
>
> thanks
> -- PMM
>
prev parent reply other threads:[~2014-03-18 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 13:39 [Qemu-devel] [PATCH for-2.0] vl.c: Fix OpenBSD compilation issue due to namespace collisions Marcel Apfelbaum
2014-03-18 13:57 ` Peter Maydell
2014-03-18 14:05 ` Marcel Apfelbaum
2014-03-18 14:27 ` Marcel Apfelbaum
2014-03-18 14:28 ` Peter Maydell
2014-03-18 14:42 ` Marcel Apfelbaum [this message]
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=1395153738.2328.11.camel@localhost.localdomain \
--to=marcel.a@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=brad@comstyle.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.