All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Weil <sw@weilnetz.de>,
	QEMU Developers <Qemu-devel@nongnu.org>,
	Liviu Ionescu <ilg@livius.net>
Subject: Re: [Qemu-devel] MinGW build
Date: Sun, 29 Nov 2015 13:03:50 +0100	[thread overview]
Message-ID: <87fuzpnhax.fsf@emacs.mitica> (raw)
In-Reply-To: <CAFEAcA_3wKd-ny=+yc5W7Q-TSH1PoRiJdi8EJo321MvJJZE21g@mail.gmail.com> (Peter Maydell's message of "Fri, 27 Nov 2015 21:05:17 +0000")

Peter Maydell <peter.maydell@linaro.org> wrote:
> On 27 November 2015 at 19:16, Stefan Weil <sw@weilnetz.de> wrote:
>> Yes, that's correct. I just did a short test and replaced "printf"
>> by "gnu_printf" in disas/libvixl/utils.h: no more warnings when MinGW
>> compiles disas/libvixl/a64/disasm-a64.cc.
>>
>> I think we can wait for a new version of libvixl which includes the fix,
>> no need for a last minute fix for QEMU 2.5. Will you report it to the
>> libvixl developers?
>
> Yes, I've reported it to them, and I agree we don't need to fix
> this for 2.5. (There are other warnings with this mingw compiler
> anyway.)

For my compiler (F23 cross-compiler) and a fairly large configuration (*)
this is the only warning.  I will test later if this fix for me.

Later, Juan.

(*): fairly large: Everything that I was able to get libraries from
     Fedora without having to cross-compile anything by hand.

  reply	other threads:[~2015-11-29 12:04 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
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 [this message]
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=87fuzpnhax.fsf@emacs.mitica \
    --to=quintela@redhat.com \
    --cc=Qemu-devel@nongnu.org \
    --cc=ilg@livius.net \
    --cc=peter.maydell@linaro.org \
    --cc=sw@weilnetz.de \
    /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.