>>> Roger Pau Monne <roger....@citrix.com> 04/15/16 8:27 PM >>> >Previously HOSTCC was always hardcoded to gcc
So what is the goal here? Be able to build on a gcc-free system? Or else, how does it matter what compiler build elements get built with? >--- a/Config.mk >+++ b/Config.mk >@@ -36,7 +36,6 @@ CONFIG_$(XEN_OS) := y >SHELL ?= /bin/sh > ># Tools to run on system hosting the build >-HOSTCC = gcc >HOSTCFLAGS = -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer >HOSTCFLAGS += -fno-strict-aliasing > >@@ -50,8 +49,10 @@ DESTDIR ?= / >clang ?= n >ifeq ($(clang),n) >gcc := y >+HOSTCC = gcc >else >gcc := n >+HOSTCC = clang >endif In particular I wonder what this means for cross builds, where someone may have installed e.g. only a cross variant of clang. That said, I'm not really opposed to the change (as it seems to be at least an incremental improvement), I only wonder whether some more thought (and change) is needed here. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
