From: Greg Kurz <groug@kaod.org>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Michael Tokarev <mjt@tls.msk.ru>,
Laurent Vivier <laurent@vivier.eu>, Greg Kurz <groug@kaod.org>
Subject: [PATCH 0/2] configure: Fixes for --cross-cc-FOO
Date: Fri, 23 Jul 2021 16:45:59 +0200 [thread overview]
Message-ID: <20210723144601.1038381-1-groug@kaod.org> (raw)
This series fixes some issues I've hit while trying to compile
TCG checks with a cross-compiler, as an alternative to using
docker.
This isn't a regression in QEMU 6.1: the issues have been around
since they got merged in QEMU 3.0. Hence clearly QEMU 6.2 material.
Greg Kurz (2):
configure: Fix trivial typo in --cross-cc-cflags-FOO
configure: Fix excessive error detection when handling --cross-cc-FOO
configure | 29 ++++++++++++++++++-----------
docs/devel/testing.rst | 2 +-
2 files changed, 19 insertions(+), 12 deletions(-)
--
2.31.1
next reply other threads:[~2021-07-23 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 14:45 Greg Kurz [this message]
2021-07-23 14:46 ` [PATCH 1/2] configure: Fix trivial typo in --cross-cc-cflags-FOO Greg Kurz
2021-07-23 14:46 ` [PATCH 2/2] configure: Fix excessive error detection when handling --cross-cc-FOO Greg Kurz
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=20210723144601.1038381-1-groug@kaod.org \
--to=groug@kaod.org \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).