Forgive me, as I'm not too familiar with the rest of the infrastructure surrounding this, but what's the motivation for disabling llvm on non-x86 given that llvm itself is available on a wide variety of platforms?
---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. (518) 881-1183 On Wed, Jan 18, 2017 at 8:54 AM, Emil Velikov <emil.l.veli...@gmail.com> wrote: > From: Emil Velikov <emil.veli...@collabora.com> > > Already implicitly handled throughout, but keep it clear and disable > gallium-llvm. > > Cc: Tobias Droste <tdro...@gmx.de> > Signed-off-by: Emil Velikov <emil.veli...@collabora.com> > --- > configure.ac | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/configure.ac b/configure.ac > index 7580fd955f..e21041434f 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -2328,6 +2328,7 @@ fi > if test "x$enable_gallium_llvm" = xauto; then > case "$host_cpu" in > i*86|x86_64|amd64) enable_gallium_llvm=yes;; > + *) enable_gallium_llvm=no;; > esac > fi > > -- > 2.11.0 > > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
