From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, Cornelia Huck <cohuck@redhat.com>,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH v3] configure: Only build s390-ccw BIOS when system emulation is built
Date: Tue, 26 Jan 2021 19:32:19 +0100 [thread overview]
Message-ID: <6bf30108-0448-9d21-608b-e7cf19f03a90@redhat.com> (raw)
In-Reply-To: <20210125165826.2894021-1-f4bug@amsat.org>
On 25/01/2021 17.58, Philippe Mathieu-Daudé wrote:
> It is pointless to build the s390-ccw BIOS when only user-mode
> emulation is built. Only build it when s390 system mode emulation
> is selected.
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> v3: Restrict to s390x host (thuth)
> v2: Restrict to s390x-softmmu target (thuth)
> ---
> configure | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index dcc5ea7d630..4751d3e352d 100755
> --- a/configure
> +++ b/configure
> @@ -5372,8 +5372,14 @@ if { test "$cpu" = "i386" || test "$cpu" = "x86_64"; } && \
> done
> fi
>
> +s390_ccw_bios=no
> +# Only build s390-ccw bios if we're targetting s390x system emulation
> +case $target_list in
> + *"s390x-softmmu"*) s390_ccw_bios=yes
> + ;;
> +esac
> # Only build s390-ccw bios if we're on s390x and the compiler has -march=z900
> -if test "$cpu" = "s390x" ; then
> +if test "$cpu" = "s390x" && test "$s390_ccw_bios" = yes; then
Looks good to me now ... but maybe it could even be done simpler (without
the case statement) by simply doing:
if test "$cpu" = "s390x" && echo "$target_list" | grep -q s390x-softmmu ; then
...
?
Thomas
prev parent reply other threads:[~2021-01-26 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 16:58 [PATCH v3] configure: Only build s390-ccw BIOS when system emulation is built Philippe Mathieu-Daudé
2021-01-26 18:32 ` Thomas Huth [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=6bf30108-0448-9d21-608b-e7cf19f03a90@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=f4bug@amsat.org \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).