From: Yonggang Luo <luoyonggang@gmail.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Yonggang Luo <luoyonggang@gmail.com>
Subject: [PATCH 0/2] Getting qemu building under msys2 properly
Date: Sat, 29 Aug 2020 00:22:44 +0800 [thread overview]
Message-ID: <20200828162246.423-1-luoyonggang@gmail.com> (raw)
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
--
2.27.0.windows.1
next reply other threads:[~2020-08-28 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 16:22 Yonggang Luo [this message]
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 ` [PATCH 0/2] Getting qemu building under msys2 properly Paolo Bonzini
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=20200828162246.423-1-luoyonggang@gmail.com \
--to=luoyonggang@gmail.com \
--cc=pbonzini@redhat.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).