Displaying 3 results from an estimated 3 matches for "llvmcellspu".
2007 Dec 23
3
[LLVMdev] Odd problem with command line options
..../ast/libast.a ../smbase/libsmbase.a
-L/home/rich/llvm-install/lib -lpthread -ldl -lm -lelf -lLLVMLinker
-lLLVMArchive -lLLVMipo -lLLVMInstrumentation -lLLVMBitWriter
-lLLVMBitReader /home/rich/llvm-install/lib/LLVMMSIL.o
/home/rich/llvm-install/lib/LLVMCBackend.o
/home/rich/llvm-install/lib/LLVMCellSPU.o
/home/rich/llvm-install/lib/LLVMMips.o
/home/rich/llvm-install/lib/LLVMARM.o
/home/rich/llvm-install/lib/LLVMIA64.o
/home/rich/llvm-install/lib/LLVMAlpha.o
/home/rich/llvm-install/lib/LLVMPowerPC.o
/home/rich/llvm-install/lib/LLVMSparc.o
/home/rich/llvm-install/lib/LLVMX86.o -lLLVMSelectio...
2008 Feb 21
0
[LLVMdev] llvm 2.2 install and ocaml bindings
...point into the source tree as you're seeing.) You could
theoretically get working .cma's by somehow building the bindings
against an installed llvm-config.
LLVMers, what's the advantage to building .o files instead of .a's for
these libs?
LLVMARM.o
LLVMAlpha.o
LLVMCBackend.o
LLVMCellSPU.o
LLVMExecutionEngine.o
LLVMIA64.o
LLVMInterpreter.o
LLVMJIT.o
LLVMMSIL.o
LLVMMips.o
LLVMPowerPC.o
LLVMSparc.o
LLVMX86.o
This wouldn't be a problem if these components used .a's instead,
since ld's search paths are set up correctly.
The options I see are:
Use archive libraries inst...
2008 Feb 21
2
[LLVMdev] llvm 2.2 install and ocaml bindings
I've run into a problem with the ocaml bindings and the jit. It builds
fine without the jit, but when I try to include it it tries to use the
c object files from the build location, instead of the install
location:
> llvm-config --libdir --libfiles engine
/opt/local/lib
/opt/local/lib/LLVMX86.o /opt/local/lib/libLLVMSelectionDAG.a
/opt/local/lib/libLLVMCodeGen.a