From: Andre Przywara <andre.przywara@arm.com>
To: riku.voipio@linaro.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] kvmtool Makefile: relax arm test
Date: Fri, 4 Sep 2015 11:10:43 +0100 [thread overview]
Message-ID: <55E96E23.2090802@arm.com> (raw)
In-Reply-To: <1441279212-8797-1-git-send-email-riku.voipio@linaro.org>
Hi Riku,
On 03/09/15 12:20, riku.voipio@linaro.org wrote:
> From: Riku Voipio <riku.voipio@linaro.org>
>
> Currently Makefile accepts only armv7l.* When building kvmtool under 32bit
> personality on Aarch64 machines, uname -m reports "armv8l", so build fails.
> We expect doing 32bit arm builds in Aarch64 to become standard the same way
> people do i386 builds on x86_64 machines.
>
> Make the sed test a little more greedy so armv8l becomes acceptable.
>
> Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
The patch looks OK to me, I just wonder how you do the actual build
within the linux32 environment?
Do you have an arm cross compiler installed and set CROSS_COMPILE? Or is
there a magic compiler (driver) which uses uname -m as well?
And what would be the difference to setting ARCH=arm as well? Just
convenience?
Cheers,
Andre.
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index 1534e6f..7b17d52 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -103,7 +103,7 @@ OBJS += hw/i8042.o
>
> # Translate uname -m into ARCH string
> ARCH ?= $(shell uname -m | sed -e s/i.86/i386/ -e s/ppc.*/powerpc/ \
> - -e s/armv7.*/arm/ -e s/aarch64.*/arm64/ -e s/mips64/mips/)
> + -e s/armv.*/arm/ -e s/aarch64.*/arm64/ -e s/mips64/mips/)
>
> ifeq ($(ARCH),i386)
> ARCH := x86
>
next prev parent reply other threads:[~2015-09-04 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 11:20 [PATCH] kvmtool Makefile: relax arm test riku.voipio
2015-09-04 10:10 ` Andre Przywara [this message]
2015-09-04 10:52 ` Riku Voipio
2015-09-04 11:06 ` Andre Przywara
2015-09-10 5:45 ` Riku Voipio
2015-09-10 10:30 ` Will Deacon
2015-09-10 10:35 ` Riku Voipio
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=55E96E23.2090802@arm.com \
--to=andre.przywara@arm.com \
--cc=kvm@vger.kernel.org \
--cc=riku.voipio@linaro.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