similar to: [LLVMdev] how to compile mingw-llvm-gcc in windows

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

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

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

Henrik Bach wrote: >> From: "Baptiste Lepilleur" >> Date: Tue, 20 Sep 2005 09:29:07 +0200 >> >> Henrik Bach wrote: >>> Hi, >>> >>> Please have a look on my private Getting started with MinGW: >>> >>> http://www.geocities.com/henrik_bach_llvm/ >> >> >> Thanks Henrik.The make line was most useful.

>From: "Baptiste Lepilleur" >Date: Tue, 20 Sep 2005 09:29:07 +0200 > >Henrik Bach wrote: >>Hi, >> >>Please have a look on my private Getting started with MinGW: >> >>http://www.geocities.com/henrik_bach_llvm/ > > >Thanks Henrik.The make line was most useful. Though, in my case I also >needed to add a -L so libimagehlp.a would be

Hello everyone! I got following error while trying to compile llvm-gcc-4.2 using mingw: ..\llvm-gcc-4.2\obj\libcpp/../../libcpp/macro.c:1165: undefined reference to `flag_iasm_blocks' stub-c.o:stub-c.c:(.debug_info+0x81a0): undefined reference to `flag_iasm_blocks' stub-c.o:stub-c.c:(.debug_info+0x81b9): undefined reference to `iasm_state' stub-c.o:stub-c.c:(.debug_info+0x81d8):

> > .... but some Pure users and many of my students do. Pure relies on > LLVM-capable compilers for its C/C++/Fortran > inlining capabilities, so being able to just point Windows users to a > binary llvm-gcc package to make that work is very convenient. Nice to be called "Pure" :-) especially with capital letter. MinGW binaries for llvm-gcc don't have Fortran

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

2011/10/18 Albert Graef <Dr.Graef at t-online.de>: > On 10/17/2011 04:44 PM, Duncan Sands wrote: >> PS: A more convincing (IMO) argument against dragonegg is that it doesn't >> work on windows.  That's because the gcc plugin architecture doesn't work >> on windows.  Takumi has been thinking about this and has been enable to >> get dragonegg to work on

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

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

I managed to build clang on mingw/msys today. Running configure, make install worked for both debug and optimized builds in general. However there were a few hitches along the way. Make would fail with: ln: creating symbolic link `/d/super/dump/code/llvm/llvm-project/llvm/build.clang/Release+Asserts/bin/clang++.exe' to `clang.exe': No such file or directory ln: creating symbolic link

Hi, Has anyone built llvm-gcc-4.2-2.9 using mingw-w64 on Windows 7 64-bit OS? The binaries available in the download website LLVM-GCC 4.2 Front End Binaries for Mingw32/x86<http://llvm.org/releases/2.9/llvm-gcc4.2-2.9-x86-mingw32.tar.bz2> do not build applications (not surprisingly) for 64-bit Windows 7 (-m64 is disabled). I am both compiling and linking an application (to produce a

Good morning. I don't understand relation between output.log and error.log. It seems all LLVM libraries are not found on linking opt.exe. Please show us logs with command lines with make VERBOSE=1 It would be better only then to touch a few files. (eg. lib/Transforms/Scalar/GVN.cpp) The warning of --export-dynamic might be harmless, and you may add the option --enable-auto-import IIRC

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 project's principal goal, among extending > the API completeness and compatibility with MSVC.

Anton Korobeynikov wrote: >> Thanks Bob and John for the response. I am having problems building >> poolalloc with my MinGW and gcc 4.4.0 setup. Running make in the poolalloc >> directory results in a bunch of "undefined reference to ..." link errors >> building Release/lib/LLVMDataStructure.dll. I looked at the command line for >> > Hrm... John, is

> Thanks Bob and John for the response. I am having problems building > poolalloc with my MinGW and gcc 4.4.0 setup. Running make in the poolalloc > directory results in a bunch of "undefined reference to ..." link errors > building Release/lib/LLVMDataStructure.dll. I looked at the command line for Hrm... John, is poolalloc a loadable module? If yes, then it won't work

reverting doesn't help. Here are the logs: http://old.nabble.com/file/p29834726/output.log output.log http://old.nabble.com/file/p29834726/error.log error.log which mingw gcc + binutils versions are known to work (or better, the one that you guys use)? -- View this message in context: http://old.nabble.com/Compiling-LLVM-2.7-with-MinGW-GCC-4.5.0-tp29810752p29834726.html Sent from the LLVM -

Hi, i'm currently building a small JIT compiler. For the language I need a runtime library for some special math functions. I think the best would be to compile the lib to bitcode and link it. The compiler should be integrated in a product and as of this, it must work under windows (VC10, 64bit). So is it possible to build the math lib with the mingw llvm-gcc build an link it later with the

Hi, i'm currently building a small JIT compiler. For the language I need a runtime library for some special math functions. I think the best would be to compile the lib to bitcode and link it. The compiler should be integrated in a product and as of this, it must work under windows (VC10, 64bit). So is it possible to build the math lib with the mingw llvm-gcc build an link it later with the