From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH] Add INSTALL file Date: Tue, 21 Oct 2014 10:48:43 +0100 Message-ID: <1413884923.23337.16.camel@citrix.com> References: <1413557458-20322-1-git-send-email-olaf@aepfle.de> <5442D1FC.4050704@linaro.org> <20141020081125.GB13325@aepfle.de> <5444FF00.6080401@linaro.org> <20141021094017.GA24647@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20141021094017.GA24647@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Olaf Hering Cc: Julien Grall , Stefano Stabellini , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Tue, 2014-10-21 at 11:40 +0200, Olaf Hering wrote: > On Mon, Oct 20, Julien Grall wrote: > > > The typical command line to build arm is: > > > > make XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf- .... > > What gets cross compiled in this case? I can imagine its just for xen > itself? I think the tools build would need a cross-pkgconfig and all > that? It is possible to cross-compile both (as it happens I do my precommit arm64 build test that way), see http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling But yes, you need a full cross build environment for the tools portion. Ian.