[Mesa-dev] [Bug 59967] New: [regression] configure: error: Could not find llvm shared libraries
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Jan 28 03:25:38 PST 2013
https://bugs.freedesktop.org/show_bug.cgi?id=59967
Priority: medium
Bug ID: 59967
CC: tstellar at gmail.com
Assignee: mesa-dev at lists.freedesktop.org
Summary: [regression] configure: error: Could not find llvm
shared libraries
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: fabio.ped at libero.it
Hardware: All
Status: NEW
Version: git
Component: Mesa core
Product: Mesa
Configure fails with:
checking for llvm-config-3.2... /usr/bin/llvm-config-3.2
checking for NOUVEAU... yes
checking for LIBUDEV... yes
checking for RADEON... yes
checking for LIBUDEV... yes
checking for RADEON... yes
checking for INTEL... yes
checking for "/usr/lib/llvm-3.2/lib/libLLVM-3.2.so"... no
checking for "/usr/lib/llvm-3.2/lib/libLLVMTarget.so"... no
configure: error: Could not find llvm shared libraries:
Please make sure you have built llvm with the --enable-shared option
and that your llvm libraries are installed in /usr/lib/llvm-3.2/lib
If you have installed your llvm libraries to a different directory you
can use the --with-llvm-prefix= configure flag to specify this directory.
NOTE: Mesa is attempting to use llvm shared libraries because you have
passed one of the following options to configure:
--with-llvm-shared-libs
--enable-opencl
If you do not want to build with llvm shared libraries and instead want to
use llvm static libraries then remove these options from your configure
invocation and reconfigure.
make: *** [debian/stamp/i686-linux-gnu-build-dri] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Full build log here:
https://launchpadlibrarian.net/129750443/buildlog_ubuntu-quantal-i386.mesa_9.1~git1301281053.87592c~gd~q_FAILEDTOBUILD.txt.gz
Note that the two libraries are missing, but
/usr/lib/llvm-3.2/lib/libLLVM-3.2.so.1 is available. I didn't bisect, but it
worked up to last week, probably it's due to the three recent llvm configure
changes.
Output of:
$ /usr/bin/llvm-config-3.2 --libs
-lLLVMAsmParser -lLLVMInstrumentation -lLLVMLinker -lLLVMArchive
-lLLVMBitReader -lLLVMDebugInfo -lLLVMJIT -lLLVMipo -lLLVMVectorize
-lLLVMBitWriter -lLLVMTableGen -lLLVMHexagonCodeGen -lLLVMHexagonAsmPrinter
-lLLVMHexagonDesc -lLLVMHexagonInfo -lLLVMNVPTXCodeGen -lLLVMNVPTXDesc
-lLLVMNVPTXInfo -lLLVMNVPTXAsmPrinter -lLLVMMBlazeDisassembler
-lLLVMMBlazeAsmParser -lLLVMMBlazeCodeGen -lLLVMMBlazeDesc -lLLVMMBlazeInfo
-lLLVMMBlazeAsmPrinter -lLLVMCppBackendCodeGen -lLLVMCppBackendInfo
-lLLVMMSP430CodeGen -lLLVMMSP430Desc -lLLVMMSP430AsmPrinter -lLLVMMSP430Info
-lLLVMXCoreCodeGen -lLLVMXCoreDesc -lLLVMXCoreInfo -lLLVMCellSPUCodeGen
-lLLVMCellSPUDesc -lLLVMCellSPUInfo -lLLVMMipsDisassembler -lLLVMMipsAsmParser
-lLLVMMipsCodeGen -lLLVMMipsDesc -lLLVMMipsInfo -lLLVMMipsAsmPrinter
-lLLVMARMDisassembler -lLLVMARMCodeGen -lLLVMARMAsmParser -lLLVMARMDesc
-lLLVMARMInfo -lLLVMARMAsmPrinter -lLLVMPowerPCCodeGen -lLLVMPowerPCDesc
-lLLVMPowerPCInfo -lLLVMPowerPCAsmPrinter -lLLVMSparcCodeGen -lLLVMSparcDesc
-lLLVMSparcInfo -lLLVMX86AsmParser -lLLVMX86Disassembler -lLLVMX86CodeGen
-lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMX86Desc -lLLVMX86Info
-lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMMCDisassembler -lLLVMMCParser
-lLLVMInterpreter -lLLVMCodeGen -lLLVMScalarOpts -lLLVMInstCombine
-lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis -lLLVMMCJIT -lLLVMRuntimeDyld
-lLLVMExecutionEngine -lLLVMTarget -lLLVMMC -lLLVMObject -lLLVMCore
-lLLVMSupport
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20130128/c7b87646/attachment.html>
More information about the mesa-dev
mailing list