From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andre Przywara Subject: Re: [PATCH] kvmtool Makefile: relax arm test Date: Fri, 4 Sep 2015 11:10:43 +0100 Message-ID: <55E96E23.2090802@arm.com> References: <1441279212-8797-1-git-send-email-riku.voipio@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: riku.voipio@linaro.org Return-path: Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:36060 "EHLO cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754483AbbIDKJZ (ORCPT ); Fri, 4 Sep 2015 06:09:25 -0400 In-Reply-To: <1441279212-8797-1-git-send-email-riku.voipio@linaro.org> Sender: kvm-owner@vger.kernel.org List-ID: Hi Riku, On 03/09/15 12:20, riku.voipio@linaro.org wrote: > From: Riku Voipio > > 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 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 >