All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-devel <qemu-devel@nongnu.org>, Stefan Weil <sw@weilnetz.de>
Subject: Re: [Qemu-devel] Problems with native Mingw-w64 build
Date: Sun, 26 Mar 2017 13:57:14 +0100	[thread overview]
Message-ID: <CAFEAcA_vArTuWDGpTeToFhjfSV1BC3BV8WhjDsZtO5uxWiarMQ@mail.gmail.com> (raw)
In-Reply-To: <d4c50e61-112c-1818-479e-494d58e361f2@ilande.co.uk>

On 26 March 2017 at 11:30, Mark Cave-Ayland
<mark.cave-ayland@ilande.co.uk> wrote:
> In order to do some testing on a Windows box, I've spent a bit of time
> this weekend setting up a mingw-w64 build environment on Windows 10
> using http://wiki.qemu-project.org/Hosts/W32 as a guideline.

I think most people prefer to use the cross-compile.
Stefan might do native compiles.

> 2) glib-compat mkdtemp() error

> This one seems to be a genuine bug since the wiki above mentions that
> 64-bit builds cannot use versions of glib > 2.22 due to a change in the
> way global symbols are managed. Since g_dir_make_tmp() only appears in
> glib 2.30 and later, we end up using the fallback code which fails
> because mkdtemp() isn't available on Windows.

Since 2.7 the minimum version of glib has been 2.30 for Windows
(documented in http://wiki.qemu-project.org/ChangeLog/2.7),
because of this g_dir_make_tmp() dependency. Unfortunately
it looks like we forgot to update configure (we didn't for 2.7
because we noticed the issue quite late in the release cycle).

thanks
-- PMM

  reply	other threads:[~2017-03-26 12:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-26 10:30 [Qemu-devel] Problems with native Mingw-w64 build Mark Cave-Ayland
2017-03-26 12:57 ` Peter Maydell [this message]
2017-03-26 19:54   ` Stefan Weil
2017-03-27  5:48     ` Mark Cave-Ayland
2017-03-27 20:19       ` Stefan Weil
2017-03-28  7:25         ` Mark Cave-Ayland
2017-03-28 15:16           ` Thomas Huth
2017-03-31 17:08             ` Mark Cave-Ayland
2017-03-31 18:38               ` Stefan Weil

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=CAFEAcA_vArTuWDGpTeToFhjfSV1BC3BV8WhjDsZtO5uxWiarMQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.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.