From: "Nick Garnett" <nick@zazzu.com>
To: xen-devel@lists.xen.org
Subject: 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: Mon, 3 Jul 2017 11:41:37 -0700 [thread overview]
Message-ID: <005701d2f42c$02a14ef0$07e3ecd0$@zazzu.com> (raw)
I was able to cross-compile the hypervisor on an amd64 host for the aarch64
target. However, I can't build the Xen toolset.
I am following the "Xen ARM with Virtualization Extensions/CrossCompiling"
page, "Build arm64 tools" section. When I execute:
"./configure --build=x86_64-unknown-linux-gnu --host=aarch64-linux-gnu", I
get the following errors:
checking for uuid_clear in -luuid... no
checking uuid.h usability... no
checking uuid.h presence... no
checking for uuid.h... no
configure: error: cannot find a valid uuid library
configure: error: ./configure failed for tools
I have installed uuid, uuid-dev uuid-runtime and uuidcdef, but continue to
get the same error.
If anyone has seen and resolved this issue, please provide details.
Regards, Nick Garnett
Zazzu Firmware Architect
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-07-03 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 18:41 Nick Garnett [this message]
2017-07-04 14: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 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
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='005701d2f42c$02a14ef0$07e3ecd0$@zazzu.com' \
--to=nick@zazzu.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 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).