xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 6 Jul 2017 13:47:44 -0700	[thread overview]
Message-ID: <001a01d2f699$1ee3a3f0$5caaebd0$@zazzu.com> (raw)
In-Reply-To: 

Sent: Thursday, July 06, 2017 12:26

> 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.

In that case, you don't need to install crossbuild_essential_arm64. 
Compiling in that chroot is like compiling directly on an ARM platforms.

My runes are usually:

./configure
make -j install-tools

This will install the tools in /usr/local/

I think the list of dependencies on the CrossCompiling page is still valid:

https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling#Configuring_an_arm64_crossbuild_chroot

____________________________________________________________________________________
[nickgarnett:170706-1225PDT]
Julian, you state:
	In that case, you don't need to install crossbuild_essential_arm64. 
	Compiling in that chroot is like compiling directly on an ARM platform.

I assume you mean if I use crossbuild it would be "like compiling directly on an ARM platform".  Correct?

What should I do (or not do), following the HOWTO in "https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling"?
	Should I use "multiarch"?

____________________________________________________________________________________
[nickgarnett:170706-1345PDT]
Following the HOWTO "https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling", resulted in the following error in the "apt-get update" step:

	#created the chroot and fixed the chroot.d descriptor file

	(zesty-arm64-cross)root# apt-get install vim-tiny wget sudo less pkgbinarymangler

	#(zesty-arm64-cross)root# vi /etc/apt/sources.list
	# added ...
	#deb [arch=arm64] http://ports.ubuntu.com/ saucy main universe

	#Since this is a cross-build chroot Recommended and Suggested packages are largely unnecessary, 
	# created /etc/apt/apt.conf.d/30norecommends containing: 
	#APT::Install-Recommends "0";
	#APT::Install-Suggests "0";

	(zesty-arm64-cross)root# dpkg --add-architecture arm64
	(zesty-arm64-cross)root# apt-get update

	Resulted in:
	Err:3 http://archive.ubuntu.com/ubuntu zesty/main arm64 Packages
	  404  Not Found [IP: 91.189.88.149 80]
	Ign:5 http://archive.ubuntu.com/ubuntu zesty/universe arm64 Packages
	Reading package lists... Done       
	E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/zesty/main/binary-arm64/Packages  
                404  Not Found [IP: 91.189.88.149 80]
	E: Some index files failed to download. They have been ignored, or old ones used instead.
____________________________________________________________________________________




_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-07-06 20:48 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
2017-07-05  8:15           ` Julien Grall
2017-07-06 19:26             ` Nick Garnett
2017-07-06 20:47             ` Nick Garnett [this message]
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='001a01d2f699$1ee3a3f0$5caaebd0$@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).