similar to: [LLVMdev] Making dll's on MinGW.

"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

Hi, I'm new to Clang / LLVM, and trying to build so that it will run natively on Windows. Used the CMake approach (thanks to whoever created the configs for this). Had to comment out "DbgInfoRemover.cpp" in one of the make files (didn't spend time to figure out why), following which CMake produced a nice working Visual Studio 2008 solution file. I opened this up in VS

Hi Reid, I don't think I've initiated a parallel build by this command: ------------------------ make TOOLLINKOPTSB+=-ldbghelp TOOLLINKOPTSB+=-lpsapi LDFLAGS+='-Wl,--no-keep-memory' -r VERBOSE=1 ------------------------ Henrik. >From: Reid Spencer Date: Wed, 26 Jan 2005 12:05:51 -0800 > >It looks like what you're getting is a sharing violation. Although, I

On Thu, Mar 10, 2005 at 01:59:12PM +0100, Henrik Bach wrote: > Here is my second try to document, how to build the llvm system for > MinGW on Windows. Thanks, Henrik! Here are some comments on your document: > Overview Does not mention the status of the CFE on MinGW. > Software on Windows If something is a list, use the HTML <ol> or <ul> tags and make it into a real

>From: Reid Spencer Date: Wed, 26 Jan 2005 12:23:49 -0800 > >Nope, unless "make" is an alias for "make -j 4" (like I have) make is make for me. > >Could you try using TOOL_VERBOSE=1 with make to get more output ? I've attached an output. Henrik. >Did you try just running the llvm-ar command by itself ? >If not, could you and give it the V (capital

Henrik Bach wrote: > Hi LLVM'ers > > When linking tblgen tool I get below error message on MinGW. > > I have put TOOLLINKOPTS=-ldbghelp in Makefile.config. > > However, when rearranging library dbghelp to the end of the g++ > line, tblgen gets linked. It seems that the -L path options are specified before the LLVM libraries (libSystem and libsupport) are linked in.

Yes, that's my understanding, too. But I'm not controlling where my library -ldbghelp is put when g++ is called. I just put it in the TOOLLINKOPTS variable in Makefile.config. Henrik >From: Reid Spencer <reid at x10sys.com> > >John Criswell wrote: >> >>It seems that the -L path options are specified before the LLVM libraries >>(libSystem and

I see that you'll have a Stack Frame object with a Call Stack being accessible from a RuntimeInfo object. I'm having trouble finding out how to access this RuntimeInfo object or the Call Stack. What is the easiest way to do this? Thanks, Ben Mayne x245 -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Thu, 2004-09-02 at 00:04, Vladimir Merzliakov wrote: > I resend email with updated (after mass header move) log examples. > > > LLVM build without big problems in obj dir == src dir case (for example, > > last night tester build) > > But I have problem with building CVS version LLVM in obj dir != src dir > > case. I *only* build with obj dir != src dir and

Hi LLVM'ers When linking tblgen tool I get below error message on MinGW. I have put TOOLLINKOPTS=-ldbghelp in Makefile.config. However, when rearranging library dbghelp to the end of the g++ line, tblgen gets linked. -------------------------- make[2]: Entering directory `/C/Projects/build/MinGW/llvm/utils/TableGen' Linking Debug executable tblgen /C/Projects/build/MinGW/llvm/mklib

Hi LLVM'ers, I can't figure out why I get this error: -------------------------------------------------- c:/MinGW/bin/../libexec/gcc/mingw32/3.4.2/collect2.exe -Bdynamic -o c:/projects/build/MinGW/llvm-1-1/Debug/bin/llc.exe /mingw/lib/crt2.o c:/MinGW/bin/../lib/gcc/mingw32/3.4.2/crtbegin.o -Lc:/projects/build/MinGW/llvm-1-1/Debug/lib -Lc:/projects/build/MinGW/llvm-1-1/Debug/bin

I resend email with updated (after mass header move) log examples. > LLVM build without big problems in obj dir == src dir case (for example, > last night tester build) > But I have problem with building CVS version LLVM in obj dir != src dir > case. > gmake[1]: Entering directory `/usr/home/wanderer/pkg/build/llvm/obj/projects' gmake[2]: Entering directory

LLVM build without big problems in obj dir == src dir case (for example, last night tester build) But I have problem with building CVS version LLVM in obj dir != src dir case. ======= Finished building ModuleMaker debug executable (without symbols) ======= gmake[2]: Leaving directory `/usr/home/wanderer/pkg/build/llvm/obj/examples/ModuleMaker' gmake[1]: Leaving directory

On 2009-10-02 21:37, Benjamin Kramer wrote: >> I had a close look at the link line, and -lpsapi is specified before >> -lLLVMSystem (which is giving the error). >> When I put -lpsapi after -lLLVMSystem, it links ok. > > I commited a fix for this problem and a modified version of Jay's > patch here: >

Duncan Pierce <duncan at duncanpierce.org> writes: > I have /lib/libimagehlp.a and /lib/libpsapi.a > > nm --defined-only /lib/libpsapi.a | grep "GetProcessMemoryInfo" - > > returns: > > 00000000 T _GetProcessMemoryInfo at 12 > 00000000 I __imp__GetProcessMemoryInfo at 12 > > And llvm-config seems to be asking for them to be picked up: > >

> > >>> d:/objs/llvm/msys/Debug/lib/libLLVMSystem.a(Process.o):e:/Downloads/llvm-trunk/lib/System/Win32/Process.inc:78: > > >>> undefined reference to `GetProcessMemoryInfo at 12' > > >> GetProcessMemoryInfo should be defined in psapi.lib, but AFAICS mingw32 > > >> doesn't have this import lib. It is included in the MS Platform SDK,

Dear list, Sorry for asking this question, but has something changed in the syntax for bwplot in Lattice? In an old publication, I used > bwplot( VOTMS ~gender |type * group, data=merge(vot,words,by="ord"), nint=30, horizontal=F, layout=c(3,3), box.ratio=0.8) which produced a lovelly 3x3 lattice plot with one

Am 02.10.2009 um 21:07 schrieb Ronald Pijnacker: > I had a close look at the link line, and -lpsapi is specified before > -lLLVMSystem (which is giving the error). > When I put -lpsapi after -lLLVMSystem, it links ok. I commited a fix for this problem and a modified version of Jay's patch here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20090928/088265.html I

Ó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

> >>> d:/objs/llvm/msys/Debug/lib/libLLVMSystem.a(Process.o):e:/Downloads/llvm-trunk/lib/System/Win32/Process.inc:78: > >>> undefined reference to `GetProcessMemoryInfo at 12' > >> GetProcessMemoryInfo should be defined in psapi.lib, but AFAICS mingw32 > >> doesn't have this import lib. It is included in the MS Platform SDK, > >> but