Marek Olšák wrote:
OpenSUSE is (was?) shipping r300g with LLVM disabled. Can you believe it?
Poor users with SWTCL chipsets... and bad reputation for us too.
---
configure.ac | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure.ac b/configure.ac
index 8989c2b..8e9f73f 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1687,10 +1687,10 @@ dnl Gallium LLVM
dnl
AC_ARG_ENABLE([gallium-llvm],
[AS_HELP_STRING([--enable-gallium-llvm],
- [build gallium LLVM support @<:@default=disabled@:>@])],
+ [build gallium LLVM support @<:@default=enabled@:>@])],
[enable_gallium_llvm="$enableval"],
[enable_gallium_llvm=auto])
-if test "x$enable_gallium_llvm" = xyes; then
+if test "x$enable_gallium_llvm" != xno; then
if test "x$LLVM_CONFIG" != xno; then
LLVM_VERSION=`$LLVM_CONFIG --version`
LLVM_CFLAGS=`$LLVM_CONFIG --cppflags`
Not that it really affects me as for r600g I can --disable-gallium-r300
enable_gallium_llvm=no
but I notice llvm doesn't behave like mesa/xorg usually does in that
following the xorg modular developers guide, setting
--prefix=
ACLOCAL
PKG_CONFIG_PATH
to a non standard xorg location doesn't work with llvm - it still tries
to build/link against /usr/lib.
This fails on boxes I have with really old xorg.
If this is intentional then fair enough.
ISTR getting llvm to build against the "right" xorg in the past, but
think it took a lot of messing around (the detail I can't recall).
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
