search for: llvmsparcv9instrsched

...g/LibDeps.txt. There are three sets of circular dependencies between LLVM libraries. If you use any library from one of these sets, you may need to pull in the rest: LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a libLLVMTransformUtils.a libLLVMipa.a LLVMSparcV9.o LLVMSparcV9InstrSched.o LLVMSparcV9ModuloSched.o LLVMSparcV9RegAlloc.o LLVMExecutionEngine.o LLVMInterpreter.o LLVMJIT.o The first set is the most problematic: It includes four *.a files, which means that certain linkers will tend to get confused unless you repeat '-l' flags. The odd entry here is l...

...usr/build/llvm-2/tools/llc/Debug/llc.o /usr/build/llvm-2/Debug/lib/LLVMCBackend .o /usr/build/llvm-2/Debug/lib/LLVMSparcV9ModuloSched.o /usr/build/llvm-2/Debug/ lib/LLVMSparcV8.o /usr/build/llvm-2/Debug/lib/LLVMSparcV9.o /usr/build/llvm-2/De bug/lib/LLVMSparcV9RegAlloc.o /usr/build/llvm-2/Debug/lib/LLVMSparcV9InstrSched. o /usr/build/llvm-2/Debug/lib/LLVMSparcV9LiveVar.o /usr/build/llvm-2/Debug/lib/L LVMX86.o /usr/build/llvm-2/Debug/lib/LLVMPowerPC.o /usr/build/llvm-2/Debug/lib/L LVMAlpha.o /usr/build/llvm-2/Debug/lib/LLVMIA64.o /usr/build/llvm-2/Debug/lib/LL VMSelectionDAG.o /usr/build/llvm-2/Debug/lib/LLVMCodeGe...

...sr/build/llvm-2/tools/llc/D ebug/llc.o /usr/build/llvm-2/Debug/lib/LLVMCBackend.o /usr/build/llvm-2/Debug/li b/LLVMSparcV9ModuloSched.o /usr/build/llvm-2/Debug/lib/LLVMSparcV8.o /usr/build/ llvm-2/Debug/lib/LLVMSparcV9.o /usr/build/llvm-2/Debug/lib/LLVMSparcV9RegAlloc.o /usr/build/llvm-2/Debug/lib/LLVMSparcV9InstrSched.o /usr/build/llvm-2/Debug/lib /LLVMSparcV9LiveVar.o /usr/build/llvm-2/Debug/lib/LLVMX86.o /usr/build/llvm-2/De bug/lib/LLVMPowerPC.o /usr/build/llvm-2/Debug/lib/LLVMAlpha.o /usr/build/llvm-2/ Debug/lib/LLVMIA64.o /usr/build/llvm-2/Debug/lib/LLVMSelectionDAG.o /usr/build/l lvm-2/Debug/lib/LLVMCodeGe...

...s of circular dependencies between LLVM libraries. > If you use any library from one of these sets, you may need to pull > in the rest: > > LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a > libLLVMTransformUtils.a libLLVMipa.a > > LLVMSparcV9.o LLVMSparcV9InstrSched.o LLVMSparcV9ModuloSched.o > LLVMSparcV9RegAlloc.o > > LLVMExecutionEngine.o LLVMInterpreter.o LLVMJIT.o > > The first set is the most problematic: It includes four *.a files, > which means that certain linkers will tend to get confused unless you > repeat '-l...

...se to match the library directory they came from. In general they should be recognizable to you. For example: libtarget.a -> libLLVMTarget.a However, a few of them changed outright to make it consistent: cwriter.o -> LLVMCBackend.o profpaths.o -> LLVMProfilePaths.o Sparcv9Sched.o -> LLVMSparcV9InstrSched.o The changes have all been made to the necessary makefiles in llvm proper, but not in any of the projects. The adjustment should be pretty straight forward: capitalize first letters and prefix with LLVM. Reid.

I did not report this first error earlier as I thought it trivial. Basically it looks like something odd is happening with the configuration and 'include/llvm/config/config.h' Getting this error on building the tools on a fresh Cygwin install and update :- $ make tools-only make[1]: Entering directory `/usr/build/llvm/lib/System' llvm[1]: Compiling Path.cpp for Debug build In file

...cies between LLVM libraries. >> If you use any library from one of these sets, you may need to pull >> in the rest: >> >> LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a >> libLLVMTransformUtils.a libLLVMipa.a >> >> LLVMSparcV9.o LLVMSparcV9InstrSched.o LLVMSparcV9ModuloSched.o >> LLVMSparcV9RegAlloc.o >> >> LLVMExecutionEngine.o LLVMInterpreter.o LLVMJIT.o >> >> The first set is the most problematic: It includes four *.a files, >> which means that certain linkers will tend to get confused unless you &gt...

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron