similar to: [LLVMdev] [PATCH] llvm-config: Use "all" components by default.

Duncan Pierce <duncan at duncanpierce.org> writes: >> > I have /lib/libimagehlp.a and /lib/libpsapi.a >> > And llvm-config seems to be asking for them to be picked up: >> > >> > -I//include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -O2 >> > -fomit-frame-pointer -Woverloaded-virtual >> > -L//lib -lpsapi -limagehlp -lm >>

Óscar Fuentes <ofv <at> wanadoo.es> writes: > Duncan Pierce <duncan <at> duncanpierce.org> writes: > > > I have /lib/libimagehlp.a and /lib/libpsapi.a > > And llvm-config seems to be asking for them to be picked up: > > > > -I//include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -O2 > > -fomit-frame-pointer -Woverloaded-virtual

Hi, I got the following error output: llvm[1]: Compiling llvm-config.cpp for Debug+Asserts build llvm-config.cpp:46:35: LibraryDependencies.inc: No such file or directory llvm-config.cpp:56: error: `AvailableComponent' was not declared in this scope llvm-config.cpp:56: error: template argument 1 is invalid llvm-config.cpp:57: error: `AvailableComponent' was not declared in this scope

On 05/12/2012 04:22 AM, Keno Fischer wrote: > in order to get ready for the upcoming LLVM 3.1 release, I checked out > the 3.1 Release branch. However, unlike with LLVM 3.0, `llvm-config > --libfiles` now also reports files that belong to targets that I did not > build (and that are thus not available). Is this expected? I can confirm this. I always build LLVM with configure

Erick, I see the problem. The llvm-config linker options are baked into the ocaml library, which is good. But for the execution engine, that link line includes the full paths to some .o files. Those paths come from llvm-config, and they vary before and after installation. (Before install, they point into the source tree as you're seeing.) You could theoretically get working

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

I am trying to compile llvm in AIX 7.1 machine.. I was able to run "gmake libs-only" and it worked well. However, gmake failed with the following error .. # pwd /usr/llvm/llvm-3.1.src/tools #gmake gmake[2]: Leaving directory `/usr/llvm/llvm-3.1.src/tools/llvm-config' gmake[2]: Entering directory `/usr/llvm/llvm-3.1.src/tools/opt' gmake[2]: *** No rule to make target

Hello, in order to get ready for the upcoming LLVM 3.1 release, I checked out the 3.1 Release branch. However, unlike with LLVM 3.0, `llvm-config --libfiles` now also reports files that belong to targets that I did not build (and that are thus not available). Is this expected? Thanks, Keno -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all, I have some code that uses the x86 JIT via the C bindings that I'm trying to migrate from targeting LLVM 2.5 to the top of tree, but I'm running into a linking problem I can't figure out. Here's how I'm invoking the JIT in 2.5. LLVMInitializeNativeTarget(); <-- for the updated version LLVMCreateMemoryBufferWithContentsOfFile("code.bc", &buffer,

"Aaron Dwyer" <llvmification at gmail.com> writes: [snip] > JITCtor and InterpCtor are both NULL, so it's obvious why I'm getting > back a NULL execution engine. I am pretty sure it's because I'm > missing a few llvm .lib or .obj files. What is the set of llvm object > files needed at link time for Win32 on X86 JIT? This is what I use on MinGW. It

Keppler, Dave wrote: > Hi all, > > I have some code that uses the x86 JIT via the C bindings that I'm trying to migrate from targeting LLVM 2.5 to the top of tree, but I'm running into a linking problem I can't figure out. > > Here's how I'm invoking the JIT in 2.5. > > LLVMInitializeNativeTarget(); <-- for the updated version >

>> I'm compiling it as follows, which completes with no errors on either >LLVM version. >> >> LLVM_CONFIG=<the llvm-config from the version I want to use> >> gcc `$LLVM_CONFIG --cflags` -o main.o -c main.c >> g++ `$LLVM_CONFIG --cflags` \ >> `$LLVM_CONFIG --ldflags` \ >> main.o `$(LLVM_CONFIG) --libfiles engine BitReader` >>

On Mon, Apr 5, 2010 at 3:27 PM, Nyx <mcheva at cs.mcgill.ca> wrote: > >>> You need to figure out how to pass -rdynamic to the linker, like I > said before. http://llvm.org/docs/tutorial/OCamlLangImpl7.html > mentions it, but I don't know enough about the ocaml build process to > say whether that'll work. > > I believe I'm already doing that, properly by

>> You need to figure out how to pass -rdynamic to the linker, like I said before. http://llvm.org/docs/tutorial/OCamlLangImpl7.html mentions it, but I don't know enough about the ocaml build process to say whether that'll work. I believe I'm already doing that, properly by passing -ccopt -rdynamic to ocamlopt: ocamlopt -cc g++ -ccopt -rdynamic -linkall $(LIBFILES) -o alpha

I put in two slightly different fixes that I believe should cover the problem: http://llvm.org/viewvc/llvm-project?view=rev&revision=156837 http://llvm.org/viewvc/llvm-project?view=rev&revision=156838 Let me know if your experience disagrees. I'll try and get these into 3.1 if Bill lets me after the buildbots give a check mark. - Daniel On Tue, May 15, 2012 at 5:38 AM, Keno

Ok, I attached it to the bug. For reference, here's what I'm using on unix as a workaround as long as this is not fixed: llvm-config --libfiles | xargs -n 1 -I {} sh -c 'test -f {} && echo {}' On Tue, May 15, 2012 at 1:07 AM, Albert Graef <Dr.Graef at t-online.de> wrote: > On 05/13/2012 02:46 AM, Keno Fischer wrote: > > Currently, there's a regression

On Sun, 2006-11-26 at 19:04 -0800, SevenThunders wrote: > Here is how it fails now: > > make[2]: Entering directory `/d/Apps/llvm/tools/llvm-config' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/d/Apps/llvm/tools/llvm-config' > The system cannot find the path specified. > make[2]: Entering directory `/d/Apps/llvm/tools/opt' >

On 11/14/2017, 01:26 AM, Chris Bieneman wrote: > Sorry for the delayed response. I've been out of town a lot lately. > > The documentation you referenced is unfortunately out of date (you might notice it still references autoconf). I'll see if I can find time to update it, but the guidance should be to use the `llvm_config` CMake function instead. The proper usage of that in the

Is there a way to query a package to see what dynamic shared libraries are loaded with it? The reason I ask is because during development, I want to unload libraries so that they can be reloaded without restarting R. I want to make it automatic so that you can just pass in the name of the package, and it will unload all the relevant shared libraries. Typically, the name of the shared library is

Reid Spencer-2 wrote: > > > Looks to me like you're not configured correctly. Either that or > llvm-config doesn't know how to construct the objdir directory properly. > That error message should have a path > like: /.../Release/lib/libLLVMTransforms.a > > To verify, try this command: > > llvm-config --obj-root > llvm-config --libfiles > > These