All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: meson: problems building under msys2/mingw-w64 native
Date: Tue, 25 Aug 2020 09:49:00 +0200	[thread overview]
Message-ID: <CABgObfZ+Z_2JAYFS3cbpcM4+5e1Fqs4sa_7j=VPofF+FMxe4Kg@mail.gmail.com> (raw)
In-Reply-To: <c04489d3-e3f6-24d0-11d4-3ad6ed4f88c9@ilande.co.uk>

[-- Attachment #1: Type: text/plain, Size: 609 bytes --]

Il lun 24 ago 2020, 22:27 Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
ha scritto:

>
> With this I can get all the way to the link phase so I think it's fairly
> close. I'm
> not sure whether these escaping/quoting problems are with meson or the way
> in which
> configure is using it?
>

You can try building with ninja to find whose fault it is.

We can get rid of ninjatool as soon as tests have been converted, but I
will look into fixing the quoting issue as well. Can you send me off list
the build.ninja file to see if the isystem problem is in Meson or ninjatool?

Paolo


>
> ATB,
>
> Mark.
>
>

[-- Attachment #2: Type: text/html, Size: 1264 bytes --]

      reply	other threads:[~2020-08-25  7:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 11:05 meson: problems building under msys2/mingw-w64 native Mark Cave-Ayland
2020-08-24 11:37 ` Gerd Hoffmann
2020-08-25  7:51   ` Mark Cave-Ayland
2020-08-25  7:54     ` Paolo Bonzini
2020-08-25  8:24       ` 罗勇刚(Yonggang Luo)
2020-08-25  8:34         ` Paolo Bonzini
2020-08-25  8:37           ` 罗勇刚(Yonggang Luo)
2020-08-25 22:14           ` Mark Cave-Ayland
2020-08-26 15:34             ` Paolo Bonzini
2020-08-27 16:07               ` Mark Cave-Ayland
2020-08-24 13:18 ` Paolo Bonzini
2020-08-24 20:26   ` Mark Cave-Ayland
2020-08-25  7:49     ` Paolo Bonzini [this message]

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='CABgObfZ+Z_2JAYFS3cbpcM4+5e1Fqs4sa_7j=VPofF+FMxe4Kg@mail.gmail.com' \
    --to=pbonzini@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --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 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.