From: Peter Maydell <peter.maydell@linaro.org>
To: Eric Blake <eblake@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] osdep.h: pull in sys/sysmacros.h for major/minor/makedev
Date: Mon, 13 Mar 2017 19:41:48 +0100 [thread overview]
Message-ID: <CAFEAcA8oFwTh1HQGZJ1uoHBzU9JcNEQKHVJAeSTNUMsZeD6vYw@mail.gmail.com> (raw)
In-Reply-To: <2e5c8c2d-35a7-a26a-bd80-379479125d9c@redhat.com>
On 13 March 2017 at 19:31, Eric Blake <eblake@redhat.com> wrote:
> Whether or not you think glibc broke things, the fact remains that the
> build is broken on current Fedora rawhide if we don't apply either this
> or the other proposed patch (the one by Christopher Covington, which
> I've now pinged)
Yes, I'm not opposed to qemu having a patch to work around this
mess. I'm just irritated that glibc makes it necessary.
thanks
-- PMM
prev parent reply other threads:[~2017-03-13 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 6:12 [Qemu-devel] [PATCH] osdep.h: pull in sys/sysmacros.h for major/minor/makedev Mike Frysinger
2017-02-10 6:15 ` no-reply
2017-02-10 9:04 ` Peter Maydell
2017-02-15 3:02 ` Mike Frysinger
2017-02-15 12:50 ` Peter Maydell
2017-03-13 18:31 ` Eric Blake
2017-03-13 18:41 ` Peter Maydell [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=CAFEAcA8oFwTh1HQGZJ1uoHBzU9JcNEQKHVJAeSTNUMsZeD6vYw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=eblake@redhat.com \
--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).