LLVM >= 135219 (git: 1abf2cb) required: http://cgit.freedesktop.org/mesa/mesa/commit/?id=9228bfb37519e4a03183ec89e82a80f39addeeeb LLVM < 134829 (git: 1afcace) and 134839 (git: 7c72c92) required: $ grep -r -n "LLVMAddTypeName" ./ ./src/gallium/drivers/llvmpipe/lp_jit.c:116: LLVMAddTypeName(gallivm->module, "texture", texture_type); ./src/gallium/drivers/llvmpipe/lp_jit.c:158: LLVMAddTypeName(gallivm->module, "context", context_type); ./src/gallium/auxiliary/draw/draw_llvm.c:287: LLVMAddTypeName(gallivm->module, struct_name, vertex_header); ./src/gallium/auxiliary/draw/draw_llvm.c:303: LLVMAddTypeName(gallivm->module, "texture", texture_type); ./src/gallium/auxiliary/draw/draw_llvm.c:306: LLVMAddTypeName(gallivm->module, "draw_jit_context", context_type); ./src/gallium/auxiliary/draw/draw_llvm.c:310: LLVMAddTypeName(gallivm->module, "buffer", buffer_type); ./src/gallium/auxiliary/draw/draw_llvm.c:314: LLVMAddTypeName(gallivm->module, "pipe_vertex_buffer", vb_type); Additional hint: LLVM < 135245 (git: ef58218) required: grep -r -n "LLVMInvalidateStructLayout" ./ ./src/gallium/drivers/llvmpipe/lp_jit.c:74: LLVMInvalidateStructLayout(gallivm->target, texture_type); ./src/gallium/drivers/llvmpipe/lp_jit.c:135: LLVMInvalidateStructLayout(gallivm->target, context_type); ./src/gallium/auxiliary/draw/draw_llvm.c:129: LLVMInvalidateStructLayout(gallivm->target, texture_type); ./src/gallium/auxiliary/draw/draw_llvm.c:196: LLVMInvalidateStructLayout(gallivm->target, context_type); ./src/gallium/auxiliary/draw/draw_llvm.c:231: LLVMInvalidateStructLayout(gallivm->target, vb_type); ./src/gallium/auxiliary/draw/draw_llvm.c:264: LLVMInvalidateStructLayout(gallivm->target, vertex_header);
Created attachment 49256 [details] [review] Build fix with llvm 3.0svn This patch should fix the build errors
http://cgit.freedesktop.org/mesa/mesa/commit/?id=3143e95353072523ff5d9c977a474a87fe3cbe57 Thanks Tobias.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.