qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Yonggang Luo <luoyonggang@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] Getting qemu building under msys2 properly
Date: Fri, 28 Aug 2020 19:41:01 +0200	[thread overview]
Message-ID: <20cd87f8-d4c7-677e-3992-57ecf3d94964@redhat.com> (raw)
In-Reply-To: <20200828162246.423-1-luoyonggang@gmail.com>

On 28/08/20 18:22, Yonggang Luo wrote:
> Convert undefsym.sh to undefsym.py and replace $PWD with $build_dir
> 
> Yonggang Luo (2):
>   meson: Convert undefsym.sh to undefsym.py
>   configure: Fix include and linkage issue on msys2
> 
>  configure           | 28 +++++++++++++++-------
>  meson.build         |  2 +-
>  scripts/undefsym.py | 57 +++++++++++++++++++++++++++++++++++++++++++++
>  scripts/undefsym.sh | 20 ----------------
>  4 files changed, 77 insertions(+), 30 deletions(-)
>  create mode 100644 scripts/undefsym.py
>  delete mode 100755 scripts/undefsym.sh
> 

Thanks Yonggang, I'll queue the first patch.

I'll keep an eye on your patch but I prefer to first have the rest of
the build (tests and possibly pc-bios) moved to meson.build.  This way
most of the references to source and build paths from Make (where spaces
are problematic) should go away and it's easier to understand the effect
of the patch.

Paolo



      parent reply	other threads:[~2020-08-28 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 16:22 [PATCH 0/2] Getting qemu building under msys2 properly Yonggang Luo
2020-08-28 16:22 ` [PATCH 1/2] meson: Convert undefsym.sh to undefsym.py Yonggang Luo
2020-08-28 16:22 ` [PATCH 2/2] configure: Fix include and linkage issue on msys2 Yonggang Luo
2020-08-28 17:41 ` 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=20cd87f8-d4c7-677e-3992-57ecf3d94964@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=luoyonggang@gmail.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).