similar to: [LLVMdev] [llvm-commits] CVS: llvm/lib/Transforms/Hello/Makefile

On Fri, 13 Apr 2007, Devang Patel wrote: > And this brings back CommandLine Error: Arugment blah defined more > than once! > > And without this, opt -load .../LLVMHello.dylib -hello does not work > on Darwin because dyld is not able to find SlowerOperationInformer ;) I think libhello should drop its use of SlowOperationInformer. -Chris > On Apr 13, 2007, at 11:28 AM, Devang

On Apr 13, 2007, at 12:28 PM, Chris Lattner wrote: > On Fri, 13 Apr 2007, Devang Patel wrote: >> And this brings back CommandLine Error: Arugment blah defined more >> than once! >> >> And without this, opt -load .../LLVMHello.dylib -hello does not work >> on Darwin because dyld is not able to find SlowerOperationInformer ;) > > I think libhello should drop

On Fri, 13 Apr 2007, Devang Patel wrote: >> I think libhello should drop its use of SlowOperationInformer. > > That'll fix Hello example. However, anyone trying to load their custom > pass will likely to run into this again. It is a long-standing issue. The deal is that libsupport (and many others) are .a files. If one of the .o files in the .a file is used by a plugin, but

Hi!! It's me again. I guess that there is a problem in the Makefile of my source code. But I don't know where. Could you please verify it? The Makefile is written like this: # Makefile for Genetic Algorithm Pass CXXFLAGS = -Wall -I/iss/fpga3/nicole/galib247/ LDFLAGS= -L/iss/fpga3/nicole/galib247/ga/ -lga -Wl,-E # Path to top level of LLVM heirarchy LEVEL=../../../ # Name of the

I built llvm-2.7 from source on FreeBSD-i386 with: ./configure --prefix=/opt && gmake It builds fine, but the Hello plugin fails to load with an unresolved symbol. $ opt -load /opt/lib/libLLVMHello.so -help Error opening '/opt/lib/libLLVMHello.so': /opt/lib/libLLVMHello.so: Undefined symbol "_ZNK4llvm4Pass5printERNS_11raw_ostreamEPKNS_6ModuleE" -load

On 2009-01-19, at 13:50, Nick Lewycky wrote: > I have an issue with the OCaml build system and the ExecutionEngine. > > PR2128 has a patch 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

Hi, I'm making my way through the WritingAnLLVMPass tutorial and hitting the following issue. $ opt -load ../../../Debug+Asserts/lib/LLVMHello.so -hello < hello.bc > /dev/null opt: symbol lookup error: ../../../Debug+Asserts/lib/LLVMHello.so: undefined symbol: AnnotateHappensAfter nm -g ../../../Debug+Asserts/lib/LLVMHello.so U AnnotateHappensAfter ... $ ldd

On 9/2/06, Chris Lattner <sabre at nondot.org> wrote: > > Make sure to add it to Codegen/LinkAllCodegenComponents.h. I'm sure I did. I did so from the first time and I also needed to add my library .a file to the USEDLIBS variable within llc makefile to build llc. I wonder how lli links with all the rest LLVM as it seems to include no lib within its makefile. May be I need to

> Looks like your shared library is not being compiled with symbols. > Did you verify that your sources are compiled with -g? I think so, this is the makefile (based on the one in the Hello pass): > LEVEL = ../../.. > LIBRARYNAME = CGF > LOADABLE_MODULE = 1 > USEDLIBS = > > ifneq ($(REQUIRES_RTTI), 1) > ifneq ($(REQUIRES_EH), 1) > EXPORTED_SYMBOL_FILE =

Chris, On Fri, 2007-04-13 at 12:39 -0700, Chris Lattner wrote: > On Fri, 13 Apr 2007, Devang Patel wrote: > >> I think libhello should drop its use of SlowOperationInformer. > > > > That'll fix Hello example. However, anyone trying to load their custom > > pass will likely to run into this again. > > It is a long-standing issue. The deal is that

On Sat, 2 Sep 2006, Anton Vayvod wrote: > I'm sure I did. I did so from the first time and I also needed to add my > library .a file to the USEDLIBS variable within llc makefile to build llc. > I wonder how lli links with all the rest LLVM as it seems to include no lib > within its makefile. May be I need to include/link my lib somewhere else? Ah, that's probably it. Try

Hi I have written a pass which creates some scheduling information. Its called MParSchedule. This pass works with opt. But when feeding it my experimental backend it seems to loose instructions and fails to work. I am loading this stuff as .so libraries under linux and i am using the amd64 version with a self compiled llvm-gcc. With this call it works: opt

This document http://llvm.org/docs/Projects.html says the USEDLIBS should be used to statically link libraries: USEDLIBSThis variable holds a space separated list of libraries that should be linked into the program. These libraries must be libraries that come from your *lib* directory. The libraries must be specified without their "lib" prefix. For example, to link libsample.a, you

Hi Takumi, > Any feedbacks are welcome. > Have fun! This seems to be pretty useful addition to LLVM on windows! And it seems the only painless way to make plugins working, yay! For me the patch looks pretty good. One minor thing: could you please rename SharedDir => SharedLibDir Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg

I have an issue with the OCaml build system and the ExecutionEngine. PR2128 has a patch 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

While learning to write LLVM passes and following the precise instructions under http://llvm.org/docs/WritingAnLLVMPass.html, <http://llvm.org/docs/WritingAnLLVMPass.html> I got this error when loading the hello pass to run the test program: opt -load ./Release/lib/Hello.so -hello < test/test.bc > /dev/null Error opening './Release/lib/Hello.so': ./Release/lib/Hello.so:

I am trying to write a MachineFunction pass and build it as a loadable module. I want the pass to run after prolog/epilog emmiter. So far, I have been using MachineFunctionPass, but by inserting it to lib/Codegen and hacking the LLVMTargetMachine file, and Pass.h files. I have created a directory "lib/Transforms/MyPass", and inside I have the code of the pass (which is just a

Hello, I just built a virgin ToT (r98634) for release on vanilla Snow Leopard. It seems that the Hello pass doesn't want to load because of undefined symbols: builddir% ../llvm/configure --prefix=$(PWD)/../installdir --enable-optimized builddir% make builddir% make install && cd ../installdir installdir% bin/opt -load lib/libLLVMHello.dylib Error opening

Hi all! I didn't manage to link my regalloc to lli (I added USEDLIBS to its makefile). Without it I can't run tests cause they need lli to be built. So how can I link createMyRegisterAllocator function to lli? Thanks. On 8/22/06, Anton Vayvod <avayvod at gmail.com> wrote: > > I managed to link my RegAlloc.a library to llc tool but can;t make the > same with lli tool.

Hi all I'm writing a pass for the llc tool. If I try to load my pass(llc -load ../mypass.so), this error message appears : Error opening '/nfs/wsi/ti/graumann/llvm-2.5/Release/lib/LLVMMicha.so': /nfs/wsi/ti/graumann/llvm-2.5/Release/lib/LLVMMicha.so: undefined symbol: _ZTVN12_GLOBAL__N_119MyRegisterAllocatorE -load request ignored. Is this code wrong for the pass