search for: libllvmhello

...34) 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 'lib/libLLVMHello.dylib': dlopen(lib/libLLVMHello.dylib, 9): Symbol not found: __ZN4llvm12FunctionPass11runOnModuleERNS_6ModuleE Referenced from: /blah/installdir/lib/libLLVMHello.dylib Expected in: flat namespace in /blah/installdir/lib/libLLVMHello.dylib -load r...

...t; 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 'lib/libLLVMHello.dylib': dlopen(lib/libLLVMHello.dylib, > 9): Symbol not found: > __ZN4llvm12FunctionPass11runOnModuleERNS_6ModuleE >  Referenced from: /blah/installdir/lib/libLLVMHello.dylib >  Expected in: flat namespace >  in /blah/installdir/lib/...

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 request ignored. OVERVIEW: llvm .bc -> .bc modular optimizer and analysis printer [...] I edited the lib/Tran...

...pt(llvm::MPPassManager::getOnTheFlyPass(llvm::Pass*, llvm::PassInfo const*, llvm::Function&)+0x62)[0x85ce85e] opt(llvm::AnalysisResolver::findImplPass(llvm::Pass*, llvm::PassInfo const*, llvm::Function&)+0x33)[0x85cbc39] /home/zhiruz/AutoESL/AutoPilot/trunk/build/obj-Linux-x86-g++/Debug/lib/libLLVMHello.so(llvm::LoopInfo& llvm::Pass::getAnalysisID<llvm::LoopInfo>(llvm::PassInfo const*, llvm::Function&)+0x99)[0x12efc7] /home/zhiruz/AutoESL/AutoPilot/trunk/build/obj-Linux-x86-g++/Debug/lib/libLLVMHello.so(llvm::LoopInfo& llvm::Pass::getAnalysis<llvm::LoopInfo>(llvm::Function&...

...ello2>::RegisterPass llvm::RegisterPass<(anonymous namespace)::Hello2>::RegisterPass llvm::RegisterPass<(anonymous namespace)::Hello2>::~RegisterPass llvm::RegisterPass<(anonymous namespace)::Hello2>::~RegisterPass As you might expect, after 'make install' installs the libLLVMHello library, 'opt -load libLLVMHello.dylib -help' shows hello and hello2 in the pass list for the Debug version but not for the Release version. Maybe I'm misunderstanding how dynamically loadable pass modules are supposed to work, but I can't imagine that this behavior was intentional...

...inAsmPrinter.a libLLVMBlackfinCodeGen.a libLLVMBlackfinInfo.a libLLVMCBackend.a libLLVMCBackendInfo.a libLLVMCellSPUAsmPrinter.a libLLVMCellSPUCodeGen.a libLLVMCellSPUInfo.a libLLVMCodeGen.a libLLVMCore.a libLLVMCppBackend.a libLLVMCppBackendInfo.a libllvm_executionengine.a libLLVMExecutionEngine.a libLLVMHello.so libLLVMInstCombine.a libLLVMInstrumentation.a libLLVMInterpreter.a libLLVMipa.a libLLVMipo.a libLLVMJIT.a libLLVMLinker.a libLLVMMBlazeAsmPrinter.a libLLVMMBlazeCodeGen.a libLLVMMBlazeInfo.a libLLVMMC.a libLLVMMCParser.a libLLVMMipsAsmPrinter.a libLLVMMipsCodeGen.a libLLVMMipsInfo.a libLLVMMSIL....

...m/bin/llvm-ranlib %i/bin/llvm-ranlib ln -s %p/lib/llvm/bin/llvm-stub %i/bin/llvm-stub ln -s %p/lib/llvm/bin/llvmc %i/bin/llvmc ln -s %p/lib/llvm/bin/opt %i/bin/opt << SplitOff: << Package: %N-shlibs Files: << lib/llvm/lib/libEnhancedDisassembly.dylib lib/llvm/lib/libLLVMHello.dylib lib/llvm/lib/libprofile_rt.dylib lib/llvm/lib/libLTO.dylib << Shlibs: << !%p/lib/llvm/lib/libEnhancedDisassembly.dylib !%p/lib/llvm/lib/libLLVMHello.dylib !%p/lib/llvm/lib/libprofile_rt.dylib %p/lib/llvm/lib/libLTO.dylib 0.0.0 %n (>= 2.7-1) 64...

Hi Tom, > I'm trying to start a project based on llvm, but am running into some > difficulties. I started with the 'LLVM Project Guide', but got hung > up in the complexities of configure.ac. I'm now using llvm-config to > provide the linker directives, but this results in undefined > references: > > $ llvm-g++ `$HOME/local/bin/llvm-config --cppflags

I'm trying to start a project based on llvm, but am running into some difficulties. I started with the 'LLVM Project Guide', but got hung up in the complexities of configure.ac. I'm now using llvm-config to provide the linker directives, but this results in undefined references: $ llvm-g++ `$HOME/local/bin/llvm-config --cppflags --ldflags --libs bitwriter` ModuleMaker.cpp

On 04/10/2010 08:01 PM, Jack Howarth wrote: > > bash-3.2$ GCC=/sw/bin/gcc-4 CC=gcc-4 CXX=g++-4 CFLAGS=-I/sw/include CXXFLAGS=-I/sw/include LLVM_CONFIG=/sw/lib/llvm/bin/llvm-config make > g++-4 -c -I/sw/lib/llvm/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -MD -MP -DIN_GCC -DREVISION=\"100954M\"

...e/lib/ LLVMPowerPCCodeGen.o /code/llvm/Release/lib/LLVMSparcCodeGen.o /code/ llvm/Release/lib/LLVMSparcAsmPrinter.o /code/llvm/Release/lib/ LLVMX86AsmPrinter.o /code/llvm/Release/lib/LLVMX86CodeGen.o is not portable! make install ... llvm[3]: Installing Release Shared Library /usr/local/lib/ libLLVMHello.dylib mklib: install: warning: remember to run `mklib --finish /code/llvm/ Release/lib' ... And that's it. Then I make a simple command-line tool in Xcode, linking to the libraries in /usr/local/lib. Here's what xcode emits: Building target “weirdbug_nolib” of project “llvmAV”...

On Sat, Apr 10, 2010 at 01:52:18PM +0200, Duncan Sands wrote: > Hi Jack, > > > Is anyone building dragon-egg on darwin? > > Anton built it once. There were some problems with dynamic libraries: gcc's > plugin support requires the use of dynamic libraries, and the configure logic > it uses thinks that darwin does not support dynamic libraries! So it is >