From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH] Add INSTALL file Date: Tue, 21 Oct 2014 14:43:07 +0200 Message-ID: <20141021124307.GA12438@aepfle.de> 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> <1413884923.23337.16.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1413884923.23337.16.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Julien Grall , Stefano Stabellini , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Tue, Oct 21, Ian Campbell wrote: > 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. Would this example work? * To build xen and tools using a cross compiler: ./configure --build=x86_64-unknown-linux-gnu --host=aarch64-linux-gnu make XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- make XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- \ DESTDIR=/some/path install Is --build= required or does configure detect this properly? Olaf