From: Wei Liu <wei.liu2@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Lars Kurth <lars.kurth@citrix.com>,
Julien Grall <julien.grall@arm.com>,
Wei Liu <wei.liu2@citrix.com>, Doug Goldstein <cardoe@cardoe.com>
Subject: [PATCH 3/3] automation: lift tools build restriction in build script
Date: Wed, 7 Nov 2018 12:31:49 +0000 [thread overview]
Message-ID: <20181107123149.4751-4-wei.liu2@citrix.com> (raw)
In-Reply-To: <20181107123149.4751-1-wei.liu2@citrix.com>
The restrictions are mostly from Travis CI days when cross-compilation
was not feasible. Now we will be building natively on Arm, remove
those lines.
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
automation/scripts/build | 6 ------
1 file changed, 6 deletions(-)
diff --git a/automation/scripts/build b/automation/scripts/build
index c463b060d4..482ed48201 100755
--- a/automation/scripts/build
+++ b/automation/scripts/build
@@ -22,12 +22,6 @@ if [[ "${CC}" == "clang" ]]; then
cfgargs+=("--disable-stubdom")
fi
-if [[ "${XEN_TARGET_ARCH}" == "arm64" || "${XEN_TARGET_ARCH}" == "arm32" ]]; then
- cfgargs+=("--disable-tools") # we don't have the cross depends installed
-elif [[ "${CC}" != "clang" ]]; then
- cfgargs+=("--enable-ovmf") # build ovmf with gcc on x86, arm doesn't use in-tree ovmf
-fi
-
./configure "${cfgargs[@]}"
make -j$(nproc) dist
--
2.11.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-11-07 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 12:31 [PATCH 0/3] automation: build Xen on Arm64 Wei Liu
2018-11-07 12:31 ` [PATCH 1/3] automation: add debian unstable arm64v8 image Wei Liu
2018-11-07 12:31 ` [PATCH 2/3] automation: add two Arm64 builds to Gitlab CI Wei Liu
2018-11-07 12:42 ` Andrew Cooper
2018-11-07 12:45 ` Wei Liu
2018-11-07 12:31 ` Wei Liu [this message]
2018-11-13 13:01 ` [PATCH 0/3] automation: build Xen on Arm64 Wei Liu
2018-11-13 13:40 ` Doug Goldstein
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=20181107123149.4751-4-wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=cardoe@cardoe.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth@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).