All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] Add INSTALL file
Date: Mon, 20 Oct 2014 13:24:32 +0100	[thread overview]
Message-ID: <5444FF00.6080401@linaro.org> (raw)
In-Reply-To: <20141020081125.GB13325@aepfle.de>

Hi Olaf,

On 10/20/2014 09:11 AM, Olaf Hering wrote:
> On Sat, Oct 18, Julien Grall wrote:
> 
>> On 17/10/2014 15:50, Olaf Hering wrote:
>>> +Variables recognized by make
>>> +==========================
>>
>> There is a bunch of variables missing in this section such as:
>>    - XEN_TARGET_ARCH: specify for which architecture we want to build Xen
>>    - CROSS_COMPILE: prefix of the toolchain (including the trailing dash
>> "-")
>>
>> This is very useful for compiling Xen ARM as it may be very slow to compile
>> on the board.
> 
> Do you have an example? Perhaps such thing should be added to the
> Example section. So far I have not attempted a build on ARM.

The typical command line to build arm is:

make XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf- ....


If the user want to build arm64:

make XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-

The parameter CROSS_COMPILE needs to be modified following the toolchain
used by the user.

Regards,



-- 
Julien Grall

  reply	other threads:[~2014-10-20 12:24 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 [this message]
2014-10-21  9:40       ` Olaf Hering
2014-10-21  9:48         ` Ian Campbell
2014-10-21 12:43           ` Olaf Hering
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=5444FF00.6080401@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=olaf@aepfle.de \
    --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.