qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] QEMU fails to configure on non-x86 hosts with recent SDL2
Date: Mon, 5 Mar 2018 10:24:41 +0000	[thread overview]
Message-ID: <CAFEAcA8Wz4q=+HDpSG_pFHB7xKMez6hCPFodoOxoTgr1FOy5nA@mail.gmail.com> (raw)

On non-x86 hosts with SDL2 2.0.8, configure fails:


config-host.mak is out-of-date, running configure

ERROR: configure test passed without -Werror but failed with -Werror.
       This is probably a bug in the configure script. The failing command
       will be at the bottom of config.log.
       You can run configure with --disable-werror to bypass this check.

The relevant configure test is the SDL one:
#include <SDL.h>
#undef main /* We don't want SDL to override our main() */
int main( void ) { return SDL_Init (SDL_INIT_VIDEO); }

and it fails because on non-x86 platforms one of the SDL headers
triggers a -Wundef warning:

cc -Wundef -o zz9.o -I /usr/include/SDL2 -c qemu-conf.c
In file included from /usr/include/SDL2/SDL.h:38:0,
                 from qemu-conf.c:1:
/usr/include/SDL2/SDL_cpuinfo.h:63:5: warning: "HAVE_IMMINTRIN_H" is
not defined, evaluates to 0 [-Wundef]
 #if HAVE_IMMINTRIN_H && !defined(SDL_DISABLE_IMMINTRIN_H)
     ^~~~~~~~~~~~~~~~

I've reported the bug to debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892087
(who will probably forward it upstream), but since this version
of SDL is already released, I guess we need to work around it it
QEMU...

Any suggestions for how to do a workaround?

thanks
-- PMM

             reply	other threads:[~2018-03-05 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 10:24 Peter Maydell [this message]
2018-03-05 10:33 ` [Qemu-devel] QEMU fails to configure on non-x86 hosts with recent SDL2 Daniel P. Berrangé
2018-03-07 14:11   ` Gerd Hoffmann
2018-03-07 14:18     ` Peter Maydell
2018-03-07 15:42       ` Gerd Hoffmann

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='CAFEAcA8Wz4q=+HDpSG_pFHB7xKMez6hCPFodoOxoTgr1FOy5nA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=kraxel@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).