From: "Nick Garnett" <nick@zazzu.com>
To: 'Julien Grall' <julien.grall@arm.com>,
'xen-devel' <xen-devel@lists.xenproject.org>,
'Wei Liu' <wei.liu2@citrix.com>,
'Stefano Stabellini' <sstabellini@kernel.org>
Subject: Re: I was able to cross-compile the hypervisor on an amd64 host for the aarch64 target ... However, I can't build the Xen toolset
Date: Tue, 4 Jul 2017 14:59:32 -0700 [thread overview]
Message-ID: <002d01d2f510$d45d1e80$7d175b80$@zazzu.com> (raw)
In-Reply-To: <4c9b6f04-8f16-3827-fe1b-891b11ce44b8@arm.com>
From: Julien Grall [mailto:julien.grall@arm.com]
Sent: Tuesday, July 04, 2017 09:47
On 07/04/2017 05:42 PM, Nick Garnett wrote:
> I tried installing the tools with an ARM64 chroot also and had a similar issue. In that case, the package
> "crossbuild_essential_arm64" wouldn't install because it depended on a package that was not installable.
I don't use crossbuild within the chroot. My chroot contains ARM64 binaries only and QEMU is used to run ARM64 binaries.
Which distributions are you targeting?
[nickgarnett 1707041454PDT] I am using Xen 4.9.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-04 22:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 18:41 I was able to cross-compile the hypervisor on an amd64 host for the aarch64 target ... However, I can't build the Xen toolset Nick Garnett
2017-07-04 14:41 ` Wei Liu
2017-07-04 15:14 ` Julien Grall
[not found] ` <015a01d2f4e4$795ec320$6c1c4960$@zazzu.com>
2017-07-04 16:46 ` Julien Grall
2017-07-04 21:59 ` Nick Garnett [this message]
2017-07-05 8:15 ` Julien Grall
2017-07-06 19:26 ` Nick Garnett
2017-07-06 20:47 ` Nick Garnett
2017-07-06 22:56 ` Nick Garnett
2017-07-07 8:13 ` Julien Grall
-- strict thread matches above, loose matches on Subject: below --
2017-07-05 13:44 Nick Garnett
[not found] <E1dSkcD-0006cd-IU@lists.xenproject.org>
2017-07-05 14:01 ` Julien Grall
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='002d01d2f510$d45d1e80$7d175b80$@zazzu.com' \
--to=nick@zazzu.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).