similar to: [LLVMdev] Building Tools on MinGW from CVS

I was building tools just fine last weekend, but now something has changed... The problem is that it can't find some symbols: (SymSetOptions, SymInitialize, SymGetModuleBase, SymFunctionTableAccess, etc.) I looked on the Web and these functions are in Dbghelp.lib. Are they also in libimagehlp.a? (BTW: does someone know a tool to examin the exported symbols in a MinGW foo.a library?)

I'm trying to compile llvm (cvs head) on windows (WinXP sp2) using the lastest mingw, but I'm getting the link errors found below. It seems that the tools are not being linked with win32 api lib (libimagehlp.a and libpsapi.a) which defines the missing symbols. The TOOLS_VERBOSE link command is at the end of the mail and does not contain those libraries. The configure line I'm

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

Hi I've been able to semi compile (i.e. excluded code not present on the platform) the source code of the LLVM tblgen tool on the MinGW platform. However, when linking the object files the linker does not succeed: -------------------------- Linking tblgen debug executable (without symbols) C:/MinGW/msys/local/build/llvm/lib/Debug/libLLVMsystem.a(Signals.o)(.text+0x7e3): In function

Hello, Greg. You wrote Sunday, May 7, 2006, 10:46:34 PM: GP> 3. One potential point of control is the INCLUDES variable found in GP> cfrontent/gcc/Makefile.in: GP> INCLUDES = -I. -I$(@D) -I$(srcdir) -I$(srcdir)/$(@D) \ GP> -I$(srcdir)/../include @INCINTL@ Just unpack mingw32's headers & libs (w32api && mingw-runtime) into prefix directory. And configure script

Hello, Greg. You wrote Saturday, May 6, 2006, 10:54:19 PM: GP> Is it possible to build using MINGW, but without using msys? GP> All along I've been assuming that I needed msys. Unfortunately, no (especially, if you want to build gcc). LLVM and gcc uses auto* machinery, which depends on sh, sed, sort, etc. So, you should use (at least for configure) some amount of

Hello, Greg. You wrote Saturday, May 6, 2006, 10:24:16 PM: GP> If anyone has any insight I'd love to hear it. GP> Meanwhile, I'll continue to investigate... Currently I'm working on bootstrapping llvm-gcc4 on mingw32 platform. There are some serious miscompartibilities preventing build. I'll let know the results. Anyway, it's common knowledge, that msys itself have

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.

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

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

Ó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

Hello, I downloaded LLVM 2.6 and was attempting to compile it with TDM-GCC 4.4.1-tdm2-sjlj + cmake 2.6.4 and this happened: =============Console=================== C:\projects\game-editor\LLVM\build-root>mingw32-make [ 2%] Built target LLVMSystem [ 5%] Built target LLVMSupport [ 7%] Built target tblgen [ 7%] Built target intrinsics_gen [ 10%] Built target LLVMCore [ 12%] Built target

Hello, Oscar. You wrote Sunday, April 23, 2006, 8:31:14 PM: OF> Forward works ok with MinGW. Back slashes can be interpreted as escape OF> sequences by MSYS/Cygwin tools. I've succeeded in building CFE in Mingw at some 1.3-1.4 release. After, I just don't have enough time to play with LLVM. I've sent my instructions to Henrik Bach <henrik_bach_llvm at hotmail.com>, maybe

Hello, Greg. You wrote Wednesday, May 10, 2006, 3:40:43 PM: GP> checking for main in -lm... configure: error: Link tests are not allowed GP> after GCC_NO_EXECUTABLES. If my memory serves me right, this message was due to something odd happened in gccld. Maybe supplied path was wrong or something like this. I've seen this bug before, but don't remember how I've fixed it. --

Hello, all. Just found this file in my e-mail atchive, hope it will be useful for somebody. ===cut=here=== Some small rules: 1) No blankspace in the paths to the top-level directories. 2) Add paths to binaries to your system PATH variable. 3) Use short paths to top-level directories. 1. Some checks & preparations. 1) Be sure, that you're using right make version: $ make

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

Anton Korobeynikov <asl at math.spbu.ru> writes: [snip] > 2) Problem: Complains about gthr-default.h file. > Resolution: Grab gcc/gcc/gthr-win32.h file and copy it to gthr-default.h ... so --enable-threads=win32 is broken... good to know. > 3) Problem: Complains about "CL_ObjCXX" and simular ("CL_") during > compilation

Commenting out the Hello transformation I get these link errors: llvm[2]: Linking Debug Shared Library LTO.dll c:/DOCUME~1/1312888/Desktop/Workspace/llvm/llvm-top/Debug/lib/libLLVMSystem.a(Signals.o): In function `Z28LLVMUnhandledExceptionFilterP19_EXCEPTION_POINTERS': c:/DOCUME~1/1312888/Desktop/Workspace/llvm/llvm-top/lib/System/Win32/Signals.inc:164: undefined reference to

So I've been looking around for people who have built shared libraries on windows and have run in to a bit of a stumbling block. I'm able to compile without the BUILD_SHARED_LIBS flag but if I put turn the flag on as follows: cmake -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE:STRING=Release -DBUILD_SHARED_LIBS:BOOL=ON ../llvm-2.7 Then call: mingw32-make I get: ... Linking CXX

Finally, I got my hands on Windows machine again today. I extracted llvm-2.1-x86-mingw32.tar.bz2 and llvm-gcc4.0-2.1-x86-mingw32.tar.bz2 to C:\llvm (It's a bare Windows Vista installation without MinGW) Added C:\llvm\bin;C:\llvm\libexec\gcc\i686-pc-mingw32\4.0.1 to PATH (C:\llvm\libexec\gcc\i686-pc-mingw32\4.0.1 was added for cc1.exe) Downloaded