similar to: [LLVMdev] Compiling LLVM on Mingw/Cygwin

Hello, I'm trying to use LLVM on Windows, using the MinGW toolchain that comes with Cygwin (gcc -mno-cygwin, not the standalone msys package). Has anyone successfully built LLVM from sources with this toolchain? The ./configure scripts automatically detects a Cygwin environment. I've spent some time trying to let it know that it should compile for MinGW. FWIW, here's what I've

In any case, it seems that GCC 3.4.4 may be in hot water even if you did get it to compile: http://llvm.org/docs/GettingStarted.html#brokengcc -- Christopher Lamb On Aug 6, 2007, at 9:48 AM, Alain Frisch wrote: > Hello, > > I'm starting to play with LLVM today and I've trouble compiling it. > I'm > working under Windows Vista, with the gcc from Cygwin: > >

Hello, I'm starting to play with LLVM today and I've trouble compiling it. I'm working under Windows Vista, with the gcc from Cygwin: gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) Is LLVM supposed to work with this version of GCC (probably using the -mno-cygwin option to get a Mingw-like behavior)? The LLVM source tree is from the current SVN trunk. Compilation

Hello, Alain. > I'm starting to play with LLVM today and I've trouble compiling it. > I'm > working under Windows Vista, with the gcc from Cygwin: Oh, this seems to be killer mix :) GCC (at least native mingw32 port) has known problems being running on Vista. > Is LLVM supposed to work with this version of GCC (probably using the > -mno-cygwin option to get a

Can anybody offer usggestions on what to do, or where else to ask? thanks --nils. Hello, I'm trying to compile rsync under Cygwin using Mingw, but without success so far. The same problem appears in pre2. $ CC='gcc -mno-cygwin' ./configure --build=mingw32 configure: Configuring rsync 2.6.3pre1 checking build system type... i386-pc-mingw32 checking host system type...

Hello, I'm trying to compile rsync under Cygwin using Mingw, but without success so far. $ CC='gcc -mno-cygwin' ./configure --build=mingw32 configure: Configuring rsync 2.6.3pre1 checking build system type... i386-pc-mingw32 checking host system type... i386-pc-mingw32 checking target system type... i386-pc-mingw32 checking for gcc... gcc -mno-cygwin checking for C compiler default

Hello, Thanks to recent changes in the SVN, I was able to successfully build LLVM under Windows in the following environments: 1. Cygwin; 2. MinGW/MSYS; 3. "gcc -mno-cygwin" (a.k.a MinGW on Cygwin). For 3., I've had to make a few manual changes to the build system. Care is needed because non-Cygwin external commands require Windows paths and Cygwin's make does not like path

Alain, > Thanks. However, I'm specifically interested in using the MinGW compiler > shipped with Cygwin (i.e. "gcc -mno-cygwin") and using Cygwin tools > (make, ...). Of course, I could probably install MSYS/MinGW just to > compile LLVM and produce the libraries. The short answer is: don't use cygwin shell with mingw compiler to build LLVM. Reason actually is:

Antony Blakey wrote: > SVN head LLVM and Clang built out of the box for me a week ago on > MSYS/MINGW, using the following files: Ok, I tried to do the same. The compilations stops with the following error message (actually, I got to the same point in my attempt to build LLVM with the MinGW compiler shipped with Cygwin): llvm[1]: Compiling MachineLoopInfo.cpp for Debug build

Hello guys, On cygwin-1.7, I can build and test clang successfully by 3-stage. Known issues: - binaries among stage2 and stage3 do not match. (other than timestamp and checksum) investigating. - I met some warnings. I have fixes for them. - [llvm] r127241 - [llvm] http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110307/117725.html - [clang] r127283 - [clang]

On cygwin-1.7, clang and llvm can be built fine through 3 stages. With --disable-assertions (RC3's default), I saw a few warnings in llvm/lib/AsmParser/LLParser.cpp with g++-4.3.4. (and two warnings, PR9515) ...Takumi $ uname.exe -a CYGWIN_NT-6.1-WOW64 HEAVEN64 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin $ gcc --version gcc (GCC) 4.3.4 20090804 (release) 1 * Stage 1 configured by

Hello list. I am attempting to build llvm, clang, compile-rt, and lldb using Cygwin. (don't ask) I am using the 3.3 tag. I have the following problems. 1 - Running configure, PATH=/usr/bin CC=/bin/gcc CXX=/bin/g++ ../llvm-3-3/configure --enable-optimized I see the following message: configure: WARNING: mmap() of a fixed address required but not supported I have seen various postings on

>> Could you please rig Makefile.rules or something to print out the value >> of $(LLVM_ON_WIN32) ? The only way I can think of this happening is if >> that's erroneously false. This works for me: Index: Makefile.rules =================================================================== --- Makefile.rules (revision 65633) +++ Makefile.rules (working copy) @@ -298,6

On Fri, Feb 27, 2009 at 4:50 PM, Aaron Gray <aaronngray.lists at googlemail.com > wrote: > On Fri, Feb 27, 2009 at 4:32 PM, Jay Foad <jay.foad at gmail.com> wrote: > >> >> Could you please rig Makefile.rules or something to print out the value >> >> of $(LLVM_ON_WIN32) ? The only way I can think of this happening is if >> >> that's

Hi, I have successfully gotten the libshout-2.0 release to compile under gcc/MingGW ('gcc -mno-cygwin', version 'gcc (GCC) 3.3.1 (cygming special)'), after applying Leigh Smith's patches as posted on this list (http://www.xiph.org/archives/icecast-dev/0660.html). I have then generated a dll and wrapped it in JNI using the stubs from libshout-java

Hello list. I am trying to build llvm, clang, compile-rt and lldb. I am working with cygwin (don't ask). Here is my tools list. $ ../llvm-check-tools.sh make GNU Make 3.80 gcc gcc (GCC) 4.5.3 svn svn, version 1.7.10 (r1485443) Python 2.7.3 perl Summary of my perl5 (revision 5 version 14 subversion 2) configuration: m4 m4 (GNU M4) 1.4.16 autoconf autoconf (GNU Autoconf) 2.69 automake automake

On Sun, Mar 1, 2009 at 4:24 AM, Nick Lewycky <nicholas at mxc.ca> wrote: Please try this patch. I tried to copy exactly what libtool would do on Cygwin by reading the libtool source. Hi Nick, Working fine on Cygwin :) Aaron Nick Aaron Gray wrote: On Fri, Feb 27, 2009 at 4:50 PM, Aaron Gray <aaronngray.lists at googlemail.com <mailto:aaronngray.lists at

Jay Foad wrote: >>> Could you please rig Makefile.rules or something to print out the value >>> of $(LLVM_ON_WIN32) ? The only way I can think of this happening is if >>> that's erroneously false. > > This works for me: > > Index: Makefile.rules > =================================================================== > --- Makefile.rules

Aaron Gray wrote: > On Sun, Mar 1, 2009 at 4:24 AM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Please try this patch. I tried to copy exactly what libtool would do > on Cygwin by reading the libtool source. > > > Hi Nick, > > Working fine on Cygwin :) Great to hear! I've committed the fix in r65922.

i don't want to deal with CVS, so i'll just post some minor fixes along to explanations for your amusement on this list ... I. cygwin compilability cygwin doesn't yet handle threads that is compatible with icecast, but thankfully icecast supports win32 native threads. however, cygwin's preprocessor "#define"'s makes icecast confuse whether it should behave