From: Stefan Weil <sw@weilnetz.de>
To: Liviu Ionescu <ilg@livius.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] MinGW build
Date: Thu, 27 Nov 2014 21:09:42 +0100 [thread overview]
Message-ID: <54778506.5060200@weilnetz.de> (raw)
In-Reply-To: <CAC8255E-CD79-4CBB-A09F-21CCD6DA6813@livius.net>
Am 27.11.2014 um 20:57 schrieb Liviu Ionescu:
>
> On 27 Nov 2014, at 21:34, Peter Maydell <peter.maydell@linaro.org> wrote:
>
>> On 27 November 2014 at 16:43, Liviu Ionescu <ilg@livius.net> wrote:
>>> in qemu-common.h:
>>>
>>> #ifdef _WIN32
>>> #include "sysemu/os-win32.h"
>>> #endif
>>>
>>> #ifdef __MINGW32__
>>> #include "sysemu/os-win32.h"
>>> #endif
>>
>> Wait, so your mingw toolchain doesn't define _WIN32 ??
>> That seems likely to break a lot of other code that does
>> ifdef checks on _WIN32.
>
> good point!
>
> I removed the second #ifdef, and the build passed.
>
> but the countless warnings are still there :-(
>
>
> regards,
>
> Liviu
The countless warnings are "normal" because you use MinGW which is
unmaintained since several years.
There is a better alternative: use Mingw-w64. It compiles QEMU (*nearly)
without warnings, solves the ffs problem and has the additional benefit
that it supports both 32 bit and 64 bit builds.
Maybe we should drop MinGW support completely...
Cheers
Stefan
*nearly means that there are still warnings for format strings in C++
code. You won't see them if you don't install a C++ compiler, but as you
are interested in ARM and the C++ code is needed for the ARM
disassembler, you might want it.
next prev parent reply other threads:[~2014-11-27 20:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 19:55 [Qemu-devel] MinGW build Liviu Ionescu
2014-11-26 20:13 ` Peter Maydell
2014-11-26 20:19 ` Stefan Weil
2014-11-26 21:44 ` Liviu Ionescu
2014-11-27 16:43 ` Liviu Ionescu
2014-11-27 19:34 ` Peter Maydell
2014-11-27 19:57 ` Liviu Ionescu
2014-11-27 20:09 ` Stefan Weil [this message]
2014-11-27 20:14 ` Liviu Ionescu
2014-11-27 20:18 ` Peter Maydell
2014-11-27 20:27 ` Liviu Ionescu
2014-11-27 22:04 ` Peter Maydell
2014-11-28 0:30 ` Liviu Ionescu
2014-11-28 7:14 ` Stefan Weil
2014-11-28 8:41 ` Peter Maydell
2015-11-27 18:49 ` Peter Maydell
2015-11-27 19:16 ` Stefan Weil
2015-11-27 21:05 ` Peter Maydell
2015-11-29 12:03 ` Juan Quintela
2015-12-03 11:58 ` Peter Maydell
2015-12-03 14:15 ` Peter Maydell
2015-12-03 14:30 ` Juan Quintela
2015-11-30 13:24 ` Juan Quintela
2015-11-30 13:29 ` Stefan Weil
2014-11-27 20:52 ` Liviu Ionescu
2014-11-27 21:14 ` Stefan Weil
2014-11-27 21:38 ` Liviu Ionescu
2014-11-28 6:20 ` Stefan Weil
2014-11-28 6:23 ` Liviu Ionescu
2014-11-28 7:03 ` Stefan Weil
2014-12-01 10:30 ` Liviu Ionescu
2014-12-01 18:42 ` Stefan Weil
2014-12-02 18:28 ` Liviu Ionescu
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=54778506.5060200@weilnetz.de \
--to=sw@weilnetz.de \
--cc=Qemu-devel@nongnu.org \
--cc=ilg@livius.net \
--cc=peter.maydell@linaro.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.