search for: lffi

...atch to change the Interpreter to use libffi. This breaks test/Bindings/Ocaml/executionengine.ml because OCaml doesn't try to link with libffi, even though llvm-config knows that we should: $ Debug/bin/llvm-config --ldflags interpreter -L/home/nicholas/llvm-commit/Debug/lib -lpthread -lffi -ldl -lm -lelf If I run 'ocamlc' by hand and pass it '-cclib -lffi', the test succeeds, so this is the only remaining problem. Is anyone familiar with how Ocaml knows what libraries to link against? We can't just pass `llvm-config --ldflags interpreter` to ocamlc because it...

...erpreter to use libffi. This > breaks test/Bindings/Ocaml/executionengine.ml because OCaml doesn't > try to link with libffi, even though llvm-config knows that we should: > > $ Debug/bin/llvm-config --ldflags interpreter > -L/home/nicholas/llvm-commit/Debug/lib -lpthread -lffi -ldl -lm - > lelf > > If I run 'ocamlc' by hand and pass it '-cclib -lffi', the test > succeeds, so this is the only remaining problem. Is anyone familiar > with how Ocaml knows what libraries to link against? We can't just > pass `llvm-config --ldflags...

I have been working successfully with llvm-gcc for some time now with support for c/c++. Today I tried going back and reconfiguring and rebuilding with support for fortran, and I am running into problems. It seems ld cannot find -lffi. I am configuring like this: /gro/pkg/src/llvm-gcc/configure --prefix=/pkg/bin/llvm-gcc --program-prefix=llvm- --enable-llvm=/pkg/build/llvm --enable-languages=c,c++,fortran I then set LD_LIBRARY_PATH to include the path of the libs for gcc-4.3.2, add that version of gcc to the PATH, and then run...

How can I specify that LLVMInterpreter depends on 'libffi' in the Makefile? Modifying LD.Flags in Interpreter/Makefile doesn't help since llvm-config doesn't pick up on that, causing a linker error when building lli. I'd like "llvm-config --libs interpreter" return -lffi along with the LLVM libraries it lists. You'd think there would be an example of this already, but I looked and didn't find one. Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090213/3346b107/...

...jo170387 at gmail.com Mesa compilation fails if configured with: ./configure --with-dri-drivers=,swrast,nouveau --with-gallium-drivers=,swrast,nouveau Error message: /bin/sh ../../../../bin/mklib -o nouveau_dri.so.tmp -noprefix -linker 'g++' -ldflags ' -L/usr/lib64/llvm -lpthread -lffi -ldl -lm ' \ target.o ../../../../src/mesa/drivers/dri/common/utils.o ../../../../src/mesa/drivers/dri/common/dri_util.o ../../../../src/mesa/drivers/dri/common/xmlconfig.o ../../../../src/gallium/state_trackers/dri/drm/libdridrm.a ../../../../src/gallium/winsys/nouveau/drm/libnouveau...

...86_64.amd64/tools/opt/Release/Passes.o /mnt/daten/Daten/Workspace/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_64.amd64/tools/opt/Release/PrintSCC.o /mnt/daten/Daten/Workspace/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_64.amd64/tools/opt/Release/opt.o \ -lLLVM-3.5svn -lz -lpthread -lffi -ldl -lm Live child 0x1f66d60 (/mnt/daten/Daten/Workspace/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_64.amd64/Release/bin/opt) PID 25040 /mnt/daten/Daten/Workspace/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_64.amd64/tools/opt/Release/opt.o: *In function `llvm::cl::list<llvm::Pass...

>> Daniel's comments are also good. > > …success! Looks like I spoke a bit too soon. Everything works as far as the fat binaries are concerned, except that -mmacosx-version-min is set to the host’s OS version, not that of the SDK, causing errors when it tries to link against 10.6’s versions of libraries instead of 10.5’s. This patch appears to solve that; it uses the OS version

...-lLLVMObject -lLLVMMCParser -lLLVMBitReader -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMInterpreter -lLLVMJIT -lLLVMCodeGen -lLLVMScalarOpts -lLLVMInstCombine -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis -lLLVMTarget -lLLVMExecutionEngine -lLLVMMC -lLLVMCore -lLLVMSupport -lz -lpthread -lffi -ledit -ltinfo -ldl -lm -lm And the error I'm getting from dlopen is ERROR: could not load library "/home/stark/src/pgjit/pgjit.so": /home/stark/src/pgjit/pgjit.so: undefined symbol: _ZTVN10__cxxabiv120__si_class_type_infoE The NEEDED lines list all the non-llvm libraries but non...

...imeMachine/LLCM_Clang/BUILD-llvm-2.6+clang/../ llvm-2.6/include \ -I/Users/albert/NoTimeMachine/LLCM_Clang/BUILD-llvm-2.6+clang/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS \ \ -L/Users/albert/NoTimeMachine/LLCM_Clang/llvm-trunk/BUILD/Debug/lib - lpthread -lffi -lm \ -lLLVMX86Disassembler \ -lLLVMX86AsmParser \ -lLLVMMCParser \ -lLLVMX86AsmPrinter \ -lLLVMX86CodeGen \ -lLLVMSelectionDAG \ -lLLVMAsmPrinter...

...ng the .a. In configure, behind a --with-oprofile argument, I have: LIBS="$LIBS ${llvm_cv_oppath}/libopagent.a -lbfd -liberty -ldl" This causes llvm-config to print: $ ./Debug/bin/llvm-config --libs --ldflags --cxxflags -L/usr/local/google/jyasskin/llvm/oprof/dbg/Debug/lib -lpthread -lffi -ldl -lm /usr/local/lib/oprofile/libopagent.a -lbfd -liberty -ldl -I/usr/local/google/jyasskin/llvm/oprof/dbg/../src/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -g -fPIC -Woverloaded-virtual -lLLVMXCore -lLLVMSparcAsmPrinter -lLLVMSparcCodeGen -lLLVMPowerPCAsmPri...

...lib/DSA/Release/Basic.o:Basic.cpp:(.text+0x12a): undefined reference to `llvm::PointerType::get(llvm::Type const*, unsigned int)' After trying to understand Makefile.rules in the llvm directory I tried using "make LOADABLE_MODULE=1" and this time the command line includes: -lffi -lpsapi -limagehlp -lm but I still get the undefined references. It looks like the correct "-l..." option is not being generated. I'm guessing this is as you (John) think a configure problem, but being currently a Windows developer I just don't know enough about it to debug....

Bob Wilson wrote: > On Mar 6, 2010, at 7:26 AM, Patrick Sathyanathan wrote: > > >> Hi, >> >> I'm interested in using the "Data Structure Analysis" that is apparently in the "poolalloc" module according to the documentation on alias analysis in LLVM. I have downloaded and built LLVM 2.6 on MinGW but the sources do not seem to include anything

...Gen -lLLVMSystemZInfo -lLLVMTarget -lLLVMTransformUtils -lLLVMX86AsmParser -lLLVMX86AsmPrinter -lLLVMX86CodeGen -lLLVMX86Disassembler -lLLVMX86Info -lLLVMXCoreAsmPrinter -lLLVMXCoreCodeGen -lLLVMXCoreInfo -lLLVMipa -lLLVMipo -lLLVMpic16passes -Wl,--no-whole-archive -Wl,--no-undefined -lpthread -lffi -lm

...l/lib/libLLVMX86Info.a /usr/local/lib/libLLVMSupport.a /usr/local/lib/libLLVMSystem.a attribs.o stub-objc.o stub-c.o -L/usr/local/lib -L/usr/local/lib -lmpfr -lgmp ../libcpp/libcpp.a -lintl -L/usr/local/lib -liconv ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -L/usr/local/lib -lpthread -lffi -lm Undefined symbols: "_gt_ggc_r_gt_darwin_c_h", referenced from: _gt_ggc_rtab in f95-lang.o ld: symbol(s) not found collect2: ld returned 1 exit status make[3]: *** [f951] Error 1 make[2]: *** [all-stage3-gcc] Error 2 make[1]: *** [stage3-bubble] Error 2 make: *** [all] Error 2...

Look at what is in <llvm source root>/examples/Kaleidoscope/toy.cpp. This is the final version of the tutorial and worked the last time I played with 2.6. Garrison On Jan 23, 2010, at 12:21, ALbert Mietus wrote: > I ask for advice, for TheExecutionEngine === NULL, > >>> Which result's in a null-pointer for "TheExecutionEngine"; which >>> explains

...Clang/BUILD-llvm-2.6+clang/../llvm-2.6/include \ > -I/Users/albert/NoTimeMachine/LLCM_Clang/BUILD-llvm-2.6+clang/include > -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS \ > \ > -L/Users/albert/NoTimeMachine/LLCM_Clang/llvm-trunk/BUILD/Debug/lib -lpthread -lffi -lm \ > -lLLVMX86Disassembler \ > -lLLVMX86AsmParser \ > -lLLVMMCParser \ > -lLLVMX86AsmPrinter \ > -lLLVMX86CodeGen \ > -lLLVMSelectionDAG \ &g...

...poseExecutionEngine' collect2: ld returned 1 exit status $ llvm-config --libs --cflags --ldflags core analysis executionengine jit interpreter native backend engine -I/mingw/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O2 -fomit-frame-pointer -L/mingw/lib -lffi -lpsapi -limagehlp -lm -lLLVMX86AsmParser -lLLVMX86AsmPrinter -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMX86Info -lLLVMInterpreter -lLLVMJIT -lLLVMCodeGen -lLLVMScalarOpts -lLLVMTransformUtils -lLLVMipa -lLLVMExecutionEngine -lLLVMAnalysis -lLLVMTarget -lLLVMMC -lLLVMCore -lLLVM...

...he immediate problem. Signed-off-by: Jeff Layton <jlayton at samba.org> - -- Jeff Layton <jlayton at samba.org> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAku/LAgACgkQyP0gxQMdzIARMQCgsRW1MEtXsJAKl6So9CfOGxy1 ofIAn06HkxKT/lAfDZcIHjovmgNPgyKQ =LfFI -----END PGP SIGNATURE-----

I ask for advice, for TheExecutionEngine === NULL, >> Which result's in a null-pointer for "TheExecutionEngine"; which >> explains the bus-errror .. Reid Kleckner wrote: > Try changing the above line to: > std::string str; > TheExecutionEngine = > EngineBuilder(OurModuleProvider).setErrorStr(str).create(); > cout << str << '\n';

On Tue, May 4, 2010 at 5:31 PM, Yuri <yuri at tsoft.com> wrote: > Jeffrey Yasskin wrote: >>> >>> Would you try the patch at >>> http://codereview.appspot.com/download/issue968046_1.diff? It should >>> make the BSDs fall into the same path as Linux, and since you use gnu >>> ld, that should work for you. >>> >> >> Ping?