similar to: [LLVMdev] Compiling LLVM-Clang with MinGW on Windows

On 2/12/2011 6:58 PM, nullnull wrote: > I'm a Windows user, and wish to run LLVM-Clang on Windows. > In Visual Studio 2010, buidling was fairly straightforward via the > solution file from CMake. However, there is no good document (thought > I searched for an hour) how to compile LLVM with MinGW on Windows. > I generated MinGW Makefile and build directories from CMake. Ok.

Hello, Jonathan > I thought I'd messed up something related to the linker, > but I couldn't explain why XP would work using the same steps. The only thing comes to my mind seeing this: perl from msysDTK works differently (somehow) on Vista, thus llvm-config is broken which leads to missed libraries, broken dependencies, etc. I'd suggest you to compare stuff on different

Hi, this is my first post to this list, so please excuse if submitting a patch without previous discussion is considered bad form or anything similar. I encountered a bug in the CMake build while using MinGW (non-MSYS, non-CYGWIN) where the LTO_export fails with a "The syntax of the command is incorrect" error. This error was previously fixed for Windows in general using

Anton Korobeynikov wrote: > Hello, Jonathan > > >> I thought I'd messed up something related to the linker, >> but I couldn't explain why XP would work using the same steps. >> > The only thing comes to my mind seeing this: perl from msysDTK works > differently (somehow) on Vista, thus llvm-config is broken which leads > to missed libraries,

John Thompson wrote: > Hi, > > I'm trying to build clang under MingW, but I'm getting a number of > errors. Could anyone provide some hints as to what you had to do? I > got some tips from > http://blogs.tedneward.com/2008/02/24/Building+LLVM+On+Windows+Using+MinGW32.aspx, > but using the newer packages, as it's a bit old. > > The ./configure seems

Changing it to only apply to the MinGW-Makefiles generator is maybe the safest method. Though you would have to check if MINGW is only set in the Mingw-Makefiles generator and not In the MSYS-Makefiles or Cygwin generators (should be in the docs). -- Johannes S. Mueller-Roemer, MSc Wiss. Mitarbeiter - Interactive Engineering Technologies (IET) Fraunhofer-Institut für Graphische Datenverarbeitung

Hi, I'm trying to build clang under MingW, but I'm getting a number of errors. Could anyone provide some hints as to what you had to do? I got some tips from http://blogs.tedneward.com/2008/02/24/Building+LLVM+On+Windows+Using+MinGW32.aspx, but using the newer packages, as it's a bit old. The ./configure seems to run without errors. The first run of make aborts with errors like:

Kenneth Boyd <zaimoni at zaimoni.com> writes: [snip] >> That does not really surprise me about CMake, but then mingw is not a >> primary compiler on Windows, more so is VC++ or Intel, either way a >> bug should be submitted to the CMake devs. > I do not want to troll the CMake devteam, so I will not submit the bug > report without a full-blown patch. The CMake

Figuring out to insert new compiling options or changing some options are very hard for a CMake newbie. I'm working on Windows (both Visual Studio, MingW/MSYS) via CMake. In particular, I'd like to do following two things: (1) I'd like to add "-std=c++0x" for some files in lib\Transforms\Instrumentation. (I don't think it's good idea to put this option entirely) (2)

Kenneth Boyd <zaimoni at zaimoni.com> writes: > I'm indulging in this exercise to enable testing a native MingW32 build > of LLVM in Windows. If LLVM's DejaGNU usage is the same as GCC's, I'll google or ask on the MinGW mailing list how MinGW testers run the GCC testsuite, before trying to fix something that maybe is not broken. > There are more portability

Kenneth Boyd <zaimoni at zaimoni.com> writes: >> I'm seeing a failure related to circular library references while >> building LLVM with CMake and MSYS. This didn't happen on the >> past. Building with the configure script works, so it seems something >> related to CMake. Do you have any insight on this? >> > I'll get back on this tonight or

[As this is turning off-topic, feel free to switch to private email] Kenneth Boyd <zaimoni at zaimoni.com> writes: > Note that the official MinGW GCC binaries generally are not > bootstrapped; they're cross-compiled (presumably from CygWin). [In > particular, both the 3.4.5 and 4.2.1 MinGW binaries of gcc are not > bootstrapped.] I use MinGW rather than CygWin for

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > >> I'm indulging in this exercise to enable testing a native MingW32 build >> of LLVM in Windows. >> > > If LLVM's DejaGNU usage is the same as GCC's, I'll google or ask on the > MinGW mailing list how MinGW testers run the GCC testsuite, before > trying to

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > [snip] > >> My internal priority for that CMake patch is low, as I need only minimal >> patching to use the autoconf-generated configure script to build LLVM. >> Right now it's just llvm.config.in.in that needs patching (the failsafed >> GenLibDeps.pl script went in

OvermindDL1 wrote: > On Sat, Oct 11, 2008 at 7:30 AM, Kenneth Boyd <zaimoni at zaimoni.com> wrote: > >> At the absolute minimum, simple counting of the success/failure/internal >> error results requires three different exit codes, and a test driver >> capable of tallying them up and reporting all failures (unexpected >> success, unexpected failure, and

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > >> * I am seeing desynchronization between the configure-generated >> Makefiles and the CMakeFile.txt files. [e.g., llc; makefile doesn't >> have asmprinter, CMakeFile.txt does]. That much I should be able to >> construct a patch for "blind", if no-one gets to it first.

On Sat, Oct 11, 2008 at 7:30 AM, Kenneth Boyd <zaimoni at zaimoni.com> wrote: > At the absolute minimum, simple counting of the success/failure/internal > error results requires three different exit codes, and a test driver > capable of tallying them up and reporting all failures (unexpected > success, unexpected failure, and internal errors with a designated > distinct exit

Óscar Fuentes wrote: > The CMake devteam is very responsive about bug reports. They will > certainly appreciate your bug report, no patch required. > I still don't think I have enough detail to file a bug report (not sure exactly what they need to know about my system configuration to make it testable). I did go ahead (just now) and ask the main CMake mailing list which files I

I had Strawberry Perl, which was the problem. I installed the Perl from the MSYS distribution and it now works. I've enclosed a patch for the Getting Started page. Thanks for pointing me in the right direction. -John >On Wed, Aug 5, 2009 at 5:36 PM, Kenneth Boyd <zaimoni at zaimoni.com> wrote: > John Thompson wrote: > > Hi, > > > > I'm trying to build

Kenneth Boyd <zaimoni at zaimoni.com> writes: >>> * I am seeing desynchronization between the configure-generated >>> Makefiles and the CMakeFile.txt files. [e.g., llc; makefile doesn't >>> have asmprinter, CMakeFile.txt does]. That much I should be able to >>> construct a patch for "blind", if no-one gets to it first. >>>