similar to: [LLVMdev] Bootstrapping llvm-gcc4 on Mingw

Hello, Everyone. This is just brief description on building llvm-gcc4 with mingw32. It's definitely non error-free and contains many "hacks", which should be eliminated in the future. 1. Prerequisites We're building in the folowing configuration: 1.1 GCC 3.4.5: gcc -v Reading specs from f:/research/mingw/bin/../lib/gcc/mingw32/3.4.5/specs Configured with:

Evan Cheng wrote: > Hi, > > Here is the follow on patch for this problem. Please apply this from > the top of the tree and rebuild. With the patch from Chris and then the patch from you combined, the previous error disappeared, but I get another error, reduced to this: ./cc1 -fpreprocessed libgcc2.i -quiet -dumpbase libgcc2.c -mtune=pentiumpro -auxbase-strip libgcc/./_clz.o -g -O2

Vladimir Prus wrote: > So, it looks either the snapshot is not in stable state, or there's > something seriously wrong with type name handling. At this point I gave up > on quickly fixing this, so I've applied the third attached patch to LLVM, > which "fixes" this issue completely. Ah, hell, as soon as I've send this email I've updated from CVS to find that

On Wed, 3 May 2006, Anton Korobeynikov wrote: > You wrote Wednesday, May 3, 2006, 1:41:31 AM: > > CL> will fix it. If so, please let me know and I'll update my tree. If not, > CL> please get a stack trace of the failure so I can see where it is called. > Yes. This fixes the bug. ASM_OUTPUT_EXTERNAL was defined in cygming.h > and seems to be platform specific. There

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

On Thu, 16 Mar 2006, Vladimir Prus wrote: > Ah, hell, as soon as I've send this email I've updated from CVS to find that > the issue was fixed by Jim several hours after I reported the crash, by > making MachineDebugInfo don't check for empty name of type. :) > Here's what I get now: > >

I'm trying to build nanobsd. I get the error below. Any ideas? ------------------------------------------------------------- >>> stage 4.2: building libraries -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/nanobsd.soekris/ MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE=

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

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

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 Aaron, Please be aware that my instructions are directed to get the cfe to compile on mingw. I wasn't in the first place aware that you were building on the Cygwin platform. However, me and others will try to help you to compile the cfe. Please submit your compiling errors on this mailing list. Henrik. >From: "Aaron Gray" <angray at beeb.net> >Reply-To: LLVM

>Sorry for the delay. Please be aware, that these instructions has not been >used lately. However, I'll try to follow up on your questions. Thanks for getting back to me. Unfortunately I lost my Cygwin configuration and cannot even seem to get GCC 3.4.3 built on CygWin now, when I had it built before. Been trying all day to get it to work maybe I will crack it tomorrow as I have had

Hi, I have a first quick patch and a question. The patch links f951 with g++ when LLVM is enabled. It's at the end of this email. I wanted to know if I should submit patches with comments around them like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to the tree. I'd like to make it as easy as possible to apply these, so let me know any rules I should be following.

> > > I suspect this is due to the recent change by Bill (revision 46747). > > > > Bill's change only affected darwin IIRC. I don't know that anyone has > > built GOMP on linux yet, and OpenMP hasn't been widely tested at all. > > I'd suggest using --enable-languages=c,c++ > > I am seeing the same errors with just building c,c++. (linux x86,

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=us-ascii" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> <b>Reid,<br> <br> I followed the steps but got stuck as described

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:

This is an libpath problem. When xgcc runs it wants to dynamically link the libgcc.so. When you run it from the command line it will find your system libgcc.so (which works) and so you don't see the segfault. When you run xgcc from the Makefile, it will have set LD_LIBRARY_PATH to get your <cfebuilddir>/gcc directory which will find the libgcc.so that it just built, which is the one

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=utf-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Reid,<br> <br> Here's the backtrace you asked for:<br> <br>

On Sat, 23 Dec 2006, Roman wrote: > How to solve this problem? Java isn't supported. Use --enable-languages=c,c++ -Chris > $ 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 directory

Hi Robert, Please make sure that you: 1. Completely rebuild LLVM (make clean; make reconfigure; make tools-only) 2. Completely rebuild llvm-gcc (wipe out the build dir with rm -rf, configure llvm-gcc and rebuild it) If you've done that, then please enter the debugger and get a stack trace for us. You will need to: 1. Capture the xgcc compile command that failed 2. Run that command