In the current HEAD, in configure.ac: ---- 1182- [enable_gallium=yes]) 1183-if test "x$enable_gallium" = xyes; then 1184- SRC_DIRS="$SRC_DIRS gallium gallium/winsys gallium/targets" 1185: AC_CHECK_HEADER([udis86.h], [HAS_UDIS86="yes"], 1186- [HAS_UDIS86="no"]) 1187- AC_PATH_PROG([LLVM_CONFIG], [llvm-config], [no]) 1188-fi -- 1340- LLVM_LIBS="`$LLVM_CONFIG --libs jit interpreter nativecodegen bitwriter` -lstdc++" 1341- 1342- if test "x$HAS_UDIS86" != xno; then 1343: LLVM_LIBS="$LLVM_LIBS -ludis86" 1344- DEFINES="$DEFINES -DHAVE_UDIS86" 1345- fi 1346- LLVM_LDFLAGS=`$LLVM_CONFIG --ldflags` ----
This means basically that the udis86 dependency is "automagic" if you elect to build with LLVM support. I have a case here of a miscompiled udis86 (missing -fPIC, preventing relocation) on a setup where LLVM was NOT compiled with udis86. Would it be possible to make the udis86 dependency optional (ie, --with-udis86 option to ./configure)? -- Francis Galiegue, fgalie...@gmail.com "It seems obvious [...] that at least some 'business intelligence' tools invest so much intelligence on the business side that they have nothing left for generating SQL queries" (Stéphane Faroult, in "The Art of SQL", ISBN 0-596-00894-5) ------------------------------------------------------------------------------ _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
