From: Brad Smith <brad@comstyle.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"Marcel Apfelbaum" <marcel.a@redhat.com>
Subject: Re: [Qemu-devel] QEMU build broken
Date: Sun, 16 Mar 2014 11:28:52 -0400 [thread overview]
Message-ID: <5325C334.5030006@comstyle.com> (raw)
In-Reply-To: <CAFEAcA9JwB8XCjrqUshNTsdcSwyYMPWK554FjwT4n28x7gOm1Q@mail.gmail.com>
On 16/03/14 11:03 AM, Peter Maydell wrote:
> On 16 March 2014 14:33, Brad Smith <brad@comstyle.com> wrote:
>> On 16/03/14 9:26 AM, Peter Maydell wrote:
>>> Can we limit the set of system headers we're pulling in to
>>> avoid the header where OpenBSD is defining this? Generally
>>> for specific headers that clash it's nicer to just limit those to
>>> whatever file really needed those defines. I'm assuming it's
>>> not pulled in by one of the POSIX headers...
>
>> It looks like it is being pulled in via include/qemu/sockets.h
>> which includes netdb.h.
>
> Ouch, and netdb.h results in this macro getting defined?
> That seems like a bit of a namespace grab by OpenBSD's
> libc really :-(
>
> -- PMM
netdb.h pulls in sys/param.h which pulls in machine/param.h
which is a MD header and that would define something like..
#define _MACHINE amd64
#define MACHINE "amd64"
#define _MACHINE_ARCH amd64
#define MACHINE_ARCH "amd64"
There has been some relatively recent work towards improving
POSIX/SUS compliance and reducing namespace pollution with some
of the headers but it seems this has not been eliminated yet.
But most of the namespace pollution reduction has come from
theoretical issues that could come from namespace collisions.
I'm not sure if anything with this constant has come up before.
But I have mentioned this issue to the developer whom is working
on fixing / cleaning up the headers to see what he says.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next prev parent reply other threads:[~2014-03-16 15:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 13:22 [Qemu-devel] QEMU build broken Brad Smith
2014-03-16 13:26 ` Peter Maydell
2014-03-16 13:40 ` Marcel Apfelbaum
2014-03-16 14:33 ` Brad Smith
2014-03-16 15:03 ` Peter Maydell
2014-03-16 15:28 ` Brad Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-08 14:47 Brad Smith
2014-05-08 14:54 ` Peter Maydell
2014-05-09 8:57 ` Riku Voipio
2014-05-09 9:55 ` Peter Maydell
2014-05-09 17:26 ` Stacey Son
2014-05-09 23:02 ` Brad Smith
2014-05-09 23:35 ` Peter Maydell
2014-05-09 23:49 ` Brad Smith
2014-05-09 23:59 ` Peter Maydell
2014-05-10 6:25 ` Markus Armbruster
2014-05-10 6:45 ` Brad Smith
2014-05-10 7:07 ` Paolo Bonzini
2014-05-10 9:18 ` Peter Maydell
2014-05-11 0:22 ` Brad Smith
2014-05-12 9:13 ` Markus Armbruster
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=5325C334.5030006@comstyle.com \
--to=brad@comstyle.com \
--cc=afaerber@suse.de \
--cc=marcel.a@redhat.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 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 NNTP newsgroup(s).