similar to: [LLVMdev] Cannot find crt2.o with llvm-gcc on windows/mingw

I managed to get the llvm tool chain compiled on my windows machine using mingw a couple of weeks ago. When I tried to run the simple test case provided in the documentation I ran into a problem of missing object files. I attempted to compile the simple hello.c hello world application. Unfortunately I get the following $ llvm-gcc hello.c -o hello.exe ld: crt2.o: No such file: No such file

Hello, Matthew > I managed to get the llvm tool chain compiled on my windows machine > using mingw a couple of weeks ago. Have you tried to build llvm-gcc by yourself? > $ llvm-gcc hello.c -o hello.exe > ld: crt2.o: No such file: No such file or directory Normally crt*.o files are built during normal gcc build process (llvm-gcc as well). However, mingw32 runtime has its own crt*.o

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

Hello, Matthew. > > I figured that just copying the mingw crt*.o files would not > > be a good idea. > /Why not? Mingw32 crt does not depend on LLVM. /I rashly copied all the *.o files from my mingw\lib directory to the llvm\lib directory. This does enable the hello world binary to compile and to function correctly. However the byte code file does not work correctly giving:

Hi all, When I try to build llvm on windows/mingw32, I get the following error: In file included from c:/work/mingw/src/llvm/lib/System/Signals.cpp:33: c:/work/mingw/src/llvm/lib/System/Win32/Signals.inc: In function 'LONG LLVMUnhandledExceptionFilter(_EXCEPTION_POINTERS*)': c:/work/mingw/src/llvm/lib/System/Win32/Signals.inc:275: error: exception handling disabled, use -fexceptions to

Hello, Matthew. > Not with the recent build. In times past I failed miserably at this using cygwin. Maybe I should try again? Well, actually I mean: whether llvm-gcc binary under consideration was built by yourself or you're using pre-built binaries from downloads section? If you're using llvm-gcc4 binary from downloads section, mingw binary is included into tarball, you might find

/Have you tried to build llvm-gcc by yourself? /Not with the recent build. In times past I failed miserably at this using cygwin. Maybe I should try again? /Normally crt*.o files are built during normal gcc build process (llvm-gcc as well). However, mingw32 runtime has its own crt*.o files, which are included with binary distribution of llvm-gcc4 (mingw32 variant). /I thought that would be

Hello, Matthew. > My file size matches the patched file. I haven't figured out how to get 7-zip to give me checksum information on windows. Use md5sum utility. It can be successfully found via google. > I rashly copied all the *.o files from my mingw\lib directory to the llvm\lib directory. > This does enable the hello world binary to compile and to function correctly. Strange.

Hello, Matthew. > I figured as much. It would be great to get the mingw branch on > windows working, since it avoids the cygwin dll and some restrictive > licensing issues. Mingw32 branch is quite ok as the time of writing this lines :) I was able to compile Qt with llvm-gcc4 1.9 and everything was fine. So, I suppose something went wrong during unpacking tarball or something like

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

Hello: After using R, > version _ platform i386-pc-mingw32 arch x86 os Win32 system x86, Win32 status major 1 minor 3.1 year 2001 month 08 day 31 language R on NT 4.0 for some time, I have now received a new machine at

Hello, Matthew. > Hmm there is no llvm-gcc directory in either the patch file or what made it > on to my system. Furthermore there are no crt*.o files after my build until > I put them in the lib directory, which where they are in the patch file. > Again the clean must have removed them. Well. Actually you should have 2 trees: 1. One you're building LLVM in. There is directory

Hello, llvm-dev. thank you for your interest in my question. Currently, I compiled simple c source code (hello.c) in lunux and windows, and I tried to simple test . first case: hello.bc (compiled with "-emit-llvm" on windows) -> lli.exe(linux). second case: hello.bc (compiled with "-emit-llvm" on linux) -> lli.exe(windows). second case return good result. but First case

When using MinGW 4.7.0 to compile Clang on Windows, the resulting Clang binary does not correctly compile simple C++ code. This is with ToT LLVM/Clang. Clang build: $ cmake -DCMAKE_BUILD_TYPE=Debug -DLLVM_TARGETS_TO_BUILD=X86 -DLLVM_EXTERNAL_CLANG_SOURCE_DIR=<dir> -G Ninja <llvm-dir> $ ninja After building Clang, I tried to compile the following program: #include <iostream>

2011/10/6 Aaron Ballman <aaron at aaronballman.com> > On Thu, Oct 6, 2011 at 2:00 PM, Ruben Van Boxem > <vanboxem.ruben at gmail.com> wrote: > > When building LLVM/Clang, I get the following build failure: > > > > MinGW-w64 provides the necessary typedefs and declarations. I adjusted > the > > ifdef's to include a check for a the MinGW-w64-specific

Anton-- I had some problems just getting a binary of mingw to run on my Windows box, so perhaps, if you're willing, a step-by-step "download this, install it here, download this other, install it here, download this optional piece if you want X and install it here, now compile hello.cc and look at what you've got" kind of installation guide would be helpful. (I got lost between

On Thu, Oct 6, 2011 at 2:00 PM, Ruben Van Boxem <vanboxem.ruben at gmail.com> wrote: > When building LLVM/Clang, I get the following build failure: > > MinGW-w64 provides the necessary typedefs and declarations. I adjusted the > ifdef's to include a check for a the MinGW-w64-specific symbol of choice to > differentiate mingw.org vs mingw-w64. Tested on i686-w64-mingw32 and

Dear LLVM-DEV Hello I am Dueky. I knew about llvm 3 months ago, and I have studied it.. I read Document for llvm in llvm.org, and I have tried compile to source file about llvm and llvm-gcc. But I could not make a success of compile to the "mingw-llvm-gcc in windows". I saw binary file "mingw-llvm-gcc for windows" , but I couldn't find the "how to compile to the

2011/10/6 Aaron Ballman <aaron at aaronballman.com> > On Thu, Oct 6, 2011 at 2:09 PM, Ruben Van Boxem > <vanboxem.ruben at gmail.com> wrote: > > You're welcome! Please remember that MinGW-w64 does not mean it is > 64-bit. > > It provides both 32- and 64-bit headers/libs. The "w64" in the name was > > originally because that was the

Hello, Dueky > But I could not make a success of compile to the "mingw-llvm-gcc in > windows". > I saw binary file "mingw-llvm-gcc for windows" , but I couldn't find > the "how to compile to the mingw-llvm-gcc in windows". In general, compilation of llvm-gcc for mingw is the same as compilation of llvm-gcc for any other platform. However, there are