From: Peter Maydell <peter.maydell@linaro.org>
To: Brad Smith <brad@comstyle.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Eric Blake" <eblake@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] ui/egl: Silent '__HAIKU__ undefined' warnings on OpenBSD 6.1
Date: Thu, 24 Jan 2019 10:11:28 +0000 [thread overview]
Message-ID: <CAFEAcA8P5eo-VEfvQ+hJTUqWVDhqV4rH91seJUM3RBOHQfj32A@mail.gmail.com> (raw)
In-Reply-To: <777d8a79-39b8-d287-f09d-d0e2e1769536@comstyle.com>
On Thu, 24 Jan 2019 at 02:03, Brad Smith <brad@comstyle.com> wrote:
>
> https://cgit.freedesktop.org/mesa/mesa/commit/include/EGL/eglplatform.h?id=f744c6c1e28fe363474550b94af42a8b7fc1c755
>
> Unfortunately that issue has only been fixed very recently.
>
> There is a possibility of us updating from Mesa 17.3.9 to 18.3.x which
> would bring in this header fix, but I don't know how long that will be
> and it's currently held up on us switching i386 from bfd ld to lld.
>
> So this header exists as is from 6.0 to the latest, most likely next release
> (6.5) too.
>
> Honestly I think it would be better to just ignore this particular
> issue. It's
> an issue with a header outside of QEMU and it will go away in time when
> Mesa is eventually updated.
Yes; I have been ignoring this warning for a while now
in my scripts that handle looking for warnings in build logs:
https://git.linaro.org/people/peter.maydell/misc-scripts.git/commit/greplogs?id=951983351baa2f27da4f4fe432fb55bf911d17e5
thanks
-- PMM
next prev parent reply other threads:[~2019-01-24 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 1:36 [Qemu-devel] [RFC PATCH] ui/egl: Silent '__HAIKU__ undefined' warnings on OpenBSD 6.1 Philippe Mathieu-Daudé
2019-01-24 2:00 ` Kamil Rytarowski
2019-01-24 10:39 ` Philippe Mathieu-Daudé
2019-01-24 2:03 ` Brad Smith
2019-01-24 10:11 ` Peter Maydell [this message]
2019-01-24 10:38 ` Philippe Mathieu-Daudé
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=CAFEAcA8P5eo-VEfvQ+hJTUqWVDhqV4rH91seJUM3RBOHQfj32A@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=brad@comstyle.com \
--cc=eblake@redhat.com \
--cc=philmd@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).