From: Brad Smith <brad@comstyle.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Marcel Apfelbaum" <marcel.a@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] QEMU build broken
Date: Sun, 16 Mar 2014 10:33:55 -0400 [thread overview]
Message-ID: <5325B653.6020105@comstyle.com> (raw)
In-Reply-To: <CAFEAcA8OmKaKncCf7hDEQP6arQ3L=t8QPSMcgyzPcc4XNADwhA@mail.gmail.com>
On 16/03/14 9:26 AM, Peter Maydell wrote:
> On 16 March 2014 13:22, Brad Smith <brad@comstyle.com> wrote:
>> Commit 0056ae24bc36798fdd96d0b31e217e9f73896736 broke the build of QEMU and
>> this affects the 2.0.0 release too.
>>
>> http://buildbot.b1-systems.de/qemu/builders/default_openbsd_current/builds/700/steps/compile/logs/stdio
>> http://buildbot.b1-systems.de/qemu/builders/default_openbsd_4.9/builds/891/steps/compile/logs/stdio
>>
>> MACHINE and MACHINE_ARCH are used to indicate the meta arch and
>> hardware architecture.
>
> 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.
--
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 14:34 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 [this message]
2014-03-16 15:03 ` Peter Maydell
2014-03-16 15:28 ` Brad Smith
-- 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=5325B653.6020105@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 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.