From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Julien Grall <julien.grall@linaro.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] Add INSTALL file
Date: Tue, 21 Oct 2014 14:43:07 +0200 [thread overview]
Message-ID: <20141021124307.GA12438@aepfle.de> (raw)
In-Reply-To: <1413884923.23337.16.camel@citrix.com>
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
next prev parent reply other threads:[~2014-10-21 12:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 14:50 [PATCH] Add INSTALL file Olaf Hering
2014-10-18 20:47 ` Julien Grall
2014-10-20 8:11 ` Olaf Hering
2014-10-20 12:24 ` Julien Grall
2014-10-21 9:40 ` Olaf Hering
2014-10-21 9:48 ` Ian Campbell
2014-10-21 12:43 ` Olaf Hering [this message]
2014-10-20 9:10 ` Andrew Cooper
2014-10-20 9:13 ` Ian Campbell
2014-10-21 10:01 ` Olaf Hering
2014-10-21 10:17 ` Andrew Cooper
2014-10-21 12:07 ` Olaf Hering
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=20141021124307.GA12438@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.