similar to: [LLVMdev] msys/mingw32 llvm-gcc build errors

Hello, Since 2.5 is near, I have been trying to build llvm and llvm-gcc for MingW, but hit several problem (using the current trunk). First issue is that unittests don't build for MingW, the attached patch should fix it. Second issue is that llvm-gcc fails for me with the following error: /c/cygwin/home/jlerouge/buildbot/llvm-test/gcc-build/./gcc/xgcc

On Jul 30, 2008, at 11:17 AM, Julien Lerouge wrote: > Not sure if that's related, but we had two failures last night as > well: > > MacOS/Universal build failed on rev 54197, when building the x86->ppc > cross: > > cc1: warnings being treated as errors > /Users/julien/buildbot/llvm/gcc-build/src/gcc/cp/pt.c:5296: warning: > no > previous prototype for

Not sure if that's related, but we had two failures last night as well: MacOS/Universal build failed on rev 54197, when building the x86->ppc cross: cc1: warnings being treated as errors /Users/julien/buildbot/llvm/gcc-build/src/gcc/cp/pt.c:5296: warning: no previous prototype for 'outermost_tinst_level' make[2]: *** [cp/pt.o] Error 1 MingW failed on rev 54208:

So the fundamental problem I'm trying to solve is how get my cfrontend build configured properly. The usual symptom of an incorrect configuration is the inability to find various header files. Here's some example spew: $ /home/llvm_home/llvm-gcc-build/gcc/xgcc -v -B/home/llvm_home/llvm-gcc-build/gcc/ -Bc:/msys/1.0/mingw32/bin/ -Bc:/msys/1.0/mingw32/lib/ -isystem

On Tue, 2006-08-01 at 15:48 +0400, Anton Vayvod wrote: > If you're building llvm-gcc4, you don't need the runtime > libraries, so > I'd just stick with the "tools-only" build and declare > success. If > you're building llvm-gcc3, I'd suggest you switch to > llvm-gcc4 :) > > I switched to

I've blown a couple of weekends trying to build under MinGW. I can build the llvm tools with only a couple of minor hassles, but can't seem to make any headway with the C Front End Most errors I run into involve not being able to find header files. The most frustrating part is that the error messages report that the file can't be found, and then proceed to give a path to where the

Hi, I have got GCC 3.4.3 and binutils 2.15 installed on Cygwin. Had to copy as.exe to gccas.exe to get llvm-gcc to get this far. I am getting the following error message(s) :- /usr/build/llvm-gcc/gcc/xgcc -B/usr/build/llvm-gcc/gcc/ -B/usr/llvm-gcc/i686-pc- cygwin/bin/ -B/usr/llvm-gcc/i686-pc-cygwin/lib/ -isystem /usr/llvm-gcc/i686-pc-c ygwin/include -isystem

Hi, I don't seem to be able to solve this regression with llvm-gcc-4.2 on Cygwin. It is weird as I thought I had checked SVN TOT and had a good build just before the branch was corrected, so am confused. If someone more experienced with debugging could have a look at this, its like a syntax error. I have tried whittling the error down but it just moves. Trying to bisect between r98185 and

Hi, I was wondering whether anyone has attempted to port LLVM to windows running with a POSIX layer, such as cygwin? I recently tried to build and run llvm on cygwin, and I got the llvm tools working. There were a few problems in the configure script, namely the mmap test fails due to MAP_FIXED not working on windows (all other mmap() stuff works), which I simply commented out since its

On Sat, 1 May 2004, Anthony Evans wrote: > I was wondering whether anyone has attempted to port LLVM to windows > running with a POSIX layer, such as cygwin? I know that Brian once got the LLVM CVS core compiled under Cygwin, but I don't recall how well it worked. I thought he had the JIT running, but I might be wrong. > I recently tried to build and run llvm on cygwin, and I got

Problem 2: Configure: ../src/configure --prefix=/tmp/llvm/install --disable-threads --disable-nls --disable-shared --enable-languages=c,c++ --disable-c-mbchar --program-prefix=llvm- $ make make[1]: Entering directory `/tmp/llvm3/llvm/build/libiberty' make[2]: Entering directory `/tmp/llvm3/llvm/build/libiberty/testsuite' make[2]: Nothing to be done for `all'. make[2]: Leaving

> > If you're building llvm-gcc4, you don't need the runtime libraries, so > I'd just stick with the "tools-only" build and declare success. If > you're building llvm-gcc3, I'd suggest you switch to llvm-gcc4 :) I switched to llvm-gcc4 but when I run make from obj folder i run into folowing errors: Can't find a library with no dependencies at

Hello, Everyone. I'm currently trying to bootstrap llvm-gcc4 on mingw32 platform. Everything (except some small fixes) seems to be fine: stage1 finished successfully. I'm linking with debug variant of LLVM, since linker bug prevents release builds. Unfortunately, stage2 failes immediately with this cryptic message: $/f/tmp/llvm/gccbuild/gcc/xgcc -B/f/tmp/llvm/gccbuild/gcc/

I am getting an error building svn llvm-gcc on Cygwin :- /home/ang/build/llvm-gcc/./gcc/xgcc -B/home/ang/build/llvm-gcc/./gcc/ -B/usr/llv m-gcc/i686-pc-cygwin/bin/ -B/usr/llvm-gcc/i686-pc-cygwin/lib/ -isystem /usr/llvm -gcc/i686-pc-cygwin/include -isystem /usr/llvm-gcc/i686-pc-cygwin/sys-include - O2 -I/home/ang/svn/llvm-gcc/gcc/../winsup/w32api/include -O2 -g -O2 -DIN_GCC -W -Wall

Hi Aaron, Which revision are you building? Assuming TOT, it's possible this is a bug that I introduced/triggered with the name changes. I know nothing of the status of cygwin however, can you confirm that this used to work? If you use r77097, does it work? - Daniel On Sun, Jul 26, 2009 at 4:23 AM, Aaron Gray<aaronngray.lists at googlemail.com> wrote: > I am getting an error

I did not realize that '--enable-llvm' was required and that invalidates my debug build results which were built just with LLVM on the path. I am now getting a segmentation fault when doing a 'make install' on LLVM-GCC4, possibly validating my original thoughts that GCC 4.1.1 was required to build LLVM-GCC 4.0.1. I will try using GCC 4.1.1. Heres the error anyway :- make[2]:

I've managed to compile LLVM & Clang on windows using command prompt and using it in MinGW (MSYS Shell). I've done this multiple times, following many different instructions, ranging from the Getting started page for clang, the llvm.org official getting started page, and even the attached guide written by someone else on the llvmdev email list (

Hi Bill, This is probably due to the llvm-gcc merge. Please take a look. Thanks, Evan On Jul 30, 2008, at 10:04 AM, Duncan Sands wrote: > x86-64 linux, during stage3: > > xgcc -B/home/duncan/LLVM/gcc-4.2.llvm-objects/./gcc/ -B/usr/local/ > gnat-llvm/x86_64-unknown-linux-gnu/bin/ -B/usr/local/gnat-llvm/ > x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/gnat-llvm/x86_64-

I am getting an assertion firing while building TOT llvm-gcc on Cygwin in libgcc2.c :- /home/ang/build/llvm-gcc/./gcc/xgcc -B/home/ang/build/llvm-gcc/./gcc/ -B/home/an g/llvm-gcc/i686-pc-cygwin/bin/ -B/home/ang/llvm-gcc/i686-pc-cygwin/lib/ -isystem /home/ang/llvm-gcc/i686-pc-cygwin/include -isystem /home/ang/llvm-gcc/i686-pc-c ygwin/sys-include -O2

x86-64 linux, during stage3: xgcc -B/home/duncan/LLVM/gcc-4.2.llvm-objects/./gcc/ -B/usr/local/gnat-llvm/x86_64-unknown-linux-gnu/bin/ -B/usr/local/gnat-llvm/x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/gnat-llvm/x86_64-unknown-linux-gnu/include -isystem /usr/local/gnat-llvm/x86_64-unknown-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I../../../gcc-4.2.llvm/libgomp -I.