Xen now builds on x86 with Clang 3.5 and 3.8.  Update README to reflect this.

Mark Clang as no longer a permitted failure in Travis, to prevent future
regressions slipping back in.

Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com>
---
CC: Ian Campbell <ian.campb...@citrix.com>
CC: Ian Jackson <ian.jack...@eu.citrix.com>
CC: Wei Liu <wei.l...@citrix.com>
CC: Doug Goldstein <car...@cardoe.com>

N.B. Older versions of Clang are expected to work, but I currently don't have
an easy way of testing this.
---
 .travis.yml |  2 --
 README      | 15 +++++++++------
 2 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index 189d568..b84d38f 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -2,8 +2,6 @@ language: c
 dist: trusty
 sudo: required
 matrix:
-    allow_failures:
-        - compiler: clang
     include:
         - compiler: gcc
           env: XEN_TARGET_ARCH=x86_64
diff --git a/README b/README
index dd36ec8..fe2e7c6 100644
--- a/README
+++ b/README
@@ -35,13 +35,16 @@ Second, there are a number of prerequisites for building a 
Xen source
 release. Make sure you have all the following installed, either by
 visiting the project webpage or installing a pre-built package
 provided by your OS distributor:
-    * GCC
-      - For x86 4.1.2_20070115 or later
-      - For ARM 4.8 or later
     * GNU Make v3.80 or later
-    * GNU Binutils:
-      - For x86 2.16.91.0.5 or later
-      - For ARM 2.24 or later
+    * C compiler and linker:
+      - For x86:
+        - GCC 4.1.2_20070115 or later
+        - GNU Binutils 2.16.91.0.5 or later
+        or
+        - Clang/LLVM 3.5 or later
+      - For ARM:
+        - GCC 4.8 or later
+        - GNU Binutils 2.24 or later
     * Development install of zlib (e.g., zlib-dev)
     * Development install of Python v2.3 or later (e.g., python-dev)
     * Development install of curses (e.g., libncurses-dev)
-- 
2.1.4


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

Reply via email to