From: Stewart Hildebrand <Stewart.Hildebrand@dornerworks.com>
To: George John <georgeeldhojohn@gmail.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Error during cross compiling of xen by chroot
Date: Fri, 13 Jul 2018 21:11:30 +0000 [thread overview]
Message-ID: <81d1d743c73c4e6694c8e8e279ae7aaa@dornerworks.com> (raw)
In-Reply-To: <CANou6SqQutpd2T7dVhQaX1wcJCUpKoWoDNigDqYP0c_zQu2oUw@mail.gmail.com>
> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xenproject.org] On Behalf
> Of George John
> Sent: Thursday, July 5, 2018 1:41 AM
> To: xen-devel <xen-devel@lists.xenproject.org>
> Subject: [Xen-devel] Error during cross compiling of xen by chroot
>
> Hi,
> I am using chroot to cross compile xen. I am getting the error as per
> the error log. I have installed libpixman. But still this is occuring.
> what could be the possible reason?
You should be able to gather more info by setting the verbose flag for the qemu build
diff --git a/tools/Makefile b/tools/Makefile
index 67977ad..fc82f5b 100644
--- a/tools/Makefile
+++ b/tools/Makefile
@@ -280,7 +280,7 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
$(CONFIG_QEMUU_EXTRA_ARGS) \
--cpu=$(IOEMU_CPU_ARCH) \
$(IOEMU_CONFIGURE_CROSS); \
- $(MAKE) all
+ $(MAKE) V=1 all
subdir-install-qemu-xen-dir: subdir-all-qemu-xen-dir
cd qemu-xen-build; \
Sort of related: if you truly want to cross compile Xen tools for aarch64 with less dependence on chroot - see the following example around lines 224-271 https://gist.github.com/stewdk/110f43e0cc1d905fc6ed4c7e10d8d35e
Thanks,
Stewart Hildebrand
DornerWorks, Ltd.
>
> Thanks and regards,
> George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-07-13 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 5:41 Error during cross compiling of xen by chroot George John
2018-07-13 21:11 ` Stewart Hildebrand [this message]
2018-07-16 4:45 ` George John
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=81d1d743c73c4e6694c8e8e279ae7aaa@dornerworks.com \
--to=stewart.hildebrand@dornerworks.com \
--cc=georgeeldhojohn@gmail.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).