On 28/03/2019 09:55, Jan Beulich wrote: >>>> On 27.03.19 at 19:45, <julien.gr...@arm.com> wrote: >> Clang uses "-target" option for cross-compilation. > And all possible targets are always available? I'd like to point out > that CROSS_COMPILE can be used for other than actual cross > compilation, e.g. building with just an alternative tool chain > built for the same target. Dropping the $(CROSS_COMPILE) > prefixes makes this impossible afaict. Requiring suitable wrapper > scripts to be put in place would seem better to me. > > I also wonder why this change is needed for Arm, but wasn't > needed so far for x86. But perhaps no-one ever tried using it > so far ...
It seems that CROSS_COMPILE is a GNU-ism, which is not shared by the clang world. I can't find anything which will make you a $FOO-$BAR-clang binary, whereas you do typically get clang-$X aliases for the different versions of clang. Using -target is from the Clang instructions on cross compilation, which say to do it this way. https://clang.llvm.org/docs/CrossCompilation.html The targets supported will depend on the configuration Clang was compiled with, but Clang specifically opposes GCC's way of requiring the user to recompile for every different target. It is expected that a packager of clang will enable all of the supported targets in the package they distribute. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
