similar to: [LLVMdev] llvm build errors on windows/mingw32

Wow, I also meet this error before, I'll be pleasure if anyone can solve this problem, and by the way, are you using msys as the building env? It's seems that mingw/cmake is working but mingw/msys, and I didn't ever try with mingw/cygwin:) thanks. 2009/10/1, Ronald Pijnacker <pijnacker at dse.nl>: > Hi all, > > When I try to build llvm on windows/mingw32, I get the

Well, Now I get the solution. Please, someone can apply the patch. Just modify the makefile resident in lib/System But, a new error is appeared llvm[2]: Linking Debug unit test ADT 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' collect2: ld returned 1 exit status make[2]: ***

> On 2009-10-02 01:07, 罗勇刚(Yonggang Luo) wrote: > > Well, Now I get the solution. > > Please, someone can apply the patch. > > > > Just modify the makefile resident in lib/System > > > > But, a new error is appeared > > llvm[2]: Linking Debug unit test ADT > >

> >>> 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

On 2009-10-02 19:34, Ronald Pijnacker wrote: >> On 2009-10-02 01:07, 罗勇刚(Yonggang Luo) wrote: >>> 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

On 2009-10-02 01:07, 罗勇刚(Yonggang Luo) wrote: > Well, Now I get the solution. > Please, someone can apply the patch. > > Just modify the makefile resident in lib/System > > But, a new error is appeared > llvm[2]: Linking Debug unit test ADT > d:/objs/llvm/msys/Debug/lib/libLLVMSystem.a(Process.o):e:/Downloads/llvm-trunk/lib/System/Win32/Process.inc:78: > undefined

> > >>> 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,

"罗勇刚(Yonggang Luo)" <luoyonggang at gmail.com> writes: > Well, Now I get the solution. > Please, someone can apply the patch. > > Just modify the makefile resident in lib/System I'm afraid this patch is not acceptable. It activates C++ exception support unconditionally while building libLLVMSystem, which is used everywhere. You'll better investigate why

Hi Anton >> $ g++ -g tut1.cpp `llvm-config --cxxflags --ldflags --libs core` -o tut1 >> /mingw/lib/libLLVMSystem.a(Process.o):Process.cpp:(.text+0x8d): >> undefined reference to `GetProcessMemoryInfo at 12' >> collect2: ld returned 1 exit status > I believe you will need additional libraries like imagehlp and psapi. I have /lib/libimagehlp.a and /lib/libpsapi.a

Hello to all! Since nobody replied and expressed desire to take over README.mingw32, I wrote short instructions how to build wxruby with MinGW compiler in MSYS environment. Considering that wxruby can be of interest to some Ruby users not so familiar with C++ and/or wxWindows (I''m one of them :-), I included some notes on installing MinGW & MSYS, building wxWindows library, Ruby ..

I successfully built llvm using msys/mingw, but I am getting the following error when I try to build llvm-gcc using $ ../llvm-gcc4.2-2.6.source/configure --prefix=/c/Temp/msys-llvm-gcc --program- prefix=llvm- --enable-llvm=/c/Temp/msys-llvm --enable-languages=c,c++ --disable -shared $make -------------------------------------------------- gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings

Hello, Kenneth > Libraries weren't being linked in; This means, that generation of llvm-config for you is broken. I really suggest to use perl from msys-DTK, not ActivePerl. -- WBR, Anton Korobeynikov

Hello, Kenneth > Using MingW32/GCC 4.2.1 binary release, mix of Cygwin and MingW32 > auxilliary tools, ActivePerl's Perl 5.8.8; operating system Vista. I'm > not going to worry about bootstrapping llvm-gcc until I know I can > bootstrap gcc. Don't do this. Use either pure cygwin or pure mingw (with msys + msysDTK) installation. This will save bunch of time for you.

Hello, Everyone. This is just brief description on building llvm-gcc4 with mingw32. It's definitely non error-free and contains many "hacks", which should be eliminated in the future. 1. Prerequisites We're building in the folowing configuration: 1.1 GCC 3.4.5: gcc -v Reading specs from f:/research/mingw/bin/../lib/gcc/mingw32/3.4.5/specs Configured with:

2009/1/13 Anton Korobeynikov <anton at korobeynikov.info>: > Hello, Duncan > > * LD (which I took to be representative of Binutils version) 2.17.50 > 20060824 > Why you're using such old binutils? 2.18.50-20080109 definitely worked for > me (and release binaries were built so...). Thank you for your reply Anton. I'm sorry it's taken a while to get back to you.

Hello, everybody. We are working on a tool for mutation testing. The work is still in progress and far away from being done. However, we have got some results already. And we would like to share them with you. But, let me give you a brief introduction first. ### Mutation Testing In a nutshell, Mutation Testing is a way to evaluate a quality of a test suite. The approach suggests introducing a

Hello, António. 2010/9/7 António Saragga Seabra <antseabra at gmail.com>: > I’m having a few problems building the kaleidoscope example (chapter 3) > under MinGW. To build the example I use as recommended > g++ -g -O3 toy.cpp `llvm-config --cppflags --ldflags --libs core` -o toy > sh: llvm-config: command not found You need MSYS's perl to use llvm-config on mingw. Does

Hello everyone, Are there any reasons the unittests in LLVM repo are split into independent executables, e.g. ADTTests, AnalysisTests, etc. Are there any performance or easy-to-use reasons for this? I plan to migrate to GTest from a project where we have all unittests in a single executable. - Paweł -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, Duncan > $ g++ -g tut1.cpp `llvm-config --cxxflags --ldflags --libs core` -o tut1 > /mingw/lib/libLLVMSystem.a(Process.o):Process.cpp:(.text+0x8d): > undefined reference to `GetProcessMemoryInfo at 12' > collect2: ld returned 1 exit status I believe you will need additional libraries like imagehlp and psapi. -- With best regards, Anton Korobeynikov Faculty of Mathematics

Hi, I have successfully built a shared version of LLVM (both 3.0rc4 and 2.9) on Windows 7 using MinGW. From there, I thought I would run the tests located under unittests (i.e. ADTTests, AnalysisTests, ExecutionEnginetests, JITTests, SupportTests, UtilsTests and VMCoreTests). All of them pass without any problem, except for JITTests which fails on the MultiJitTest.JitPool test: