similar to: [LLVMdev] Configuring for the cfrontend build on Mingw

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

Hello, all. Just found this file in my e-mail atchive, hope it will be useful for somebody. ===cut=here=== Some small rules: 1) No blankspace in the paths to the top-level directories. 2) Add paths to binaries to your system PATH variable. 3) Use short paths to top-level directories. 1. Some checks & preparations. 1) Be sure, that you're using right make version: $ make

Hello, Greg. You wrote Saturday, May 13, 2006, 11:12:26 PM: GP> The problem is that it can't find some symbols: (SymSetOptions, GP> SymInitialize, SymGetModuleBase, SymFunctionTableAccess, etc.) GP> I looked on the Web and these functions are in Dbghelp.lib. GP> Are they also in libimagehlp.a? Yes, they are. At least im mingw-runtime 3.9 (I'm using this version). GP>

Hello, Greg. You wrote Saturday, May 6, 2006, 10:54:19 PM: GP> Is it possible to build using MINGW, but without using msys? GP> All along I've been assuming that I needed msys. Unfortunately, no (especially, if you want to build gcc). LLVM and gcc uses auto* machinery, which depends on sh, sed, sort, etc. So, you should use (at least for configure) some amount of

Hello, Greg. You wrote Saturday, May 6, 2006, 10:24:16 PM: GP> If anyone has any insight I'd love to hear it. GP> Meanwhile, I'll continue to investigate... Currently I'm working on bootstrapping llvm-gcc4 on mingw32 platform. There are some serious miscompartibilities preventing build. I'll let know the results. Anyway, it's common knowledge, that msys itself have

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

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/

Hello, Greg. You wrote Wednesday, May 10, 2006, 3:40:43 PM: GP> checking for main in -lm... configure: error: Link tests are not allowed GP> after GCC_NO_EXECUTABLES. If my memory serves me right, this message was due to something odd happened in gccld. Maybe supplied path was wrong or something like this. I've seen this bug before, but don't remember how I've fixed it. --

Hello, Chuck. You wrote Tuesday, May 16, 2006, 6:03:14 PM: C> /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: BFD C> 2.16.91 C> 20050610 assertion fail C> /netrel/src/binutils-20050610-1/bfd/cofflink.c:1926 C> make[2]: *** This is a bug in binutils also seen in mingw32 build. :( I've sent bug report to binutils bugzilla this weekend. Hope, this will be

Hello, Chuck. You wrote Tuesday, May 16, 2006, 6:03:14 PM: C> /netrel/src/binutils-20050610-1/bfd/cofflink.c:1926 C> make[2]: *** I've tracked this assertion some more deep. The problem is in LLVMSelectionDAG.o file. If I run the next lines, I've got and assertion: ld -r -o LLVMSelectionDAG.o ScheduleDAGList.o ScheduleDAGRRList.o ld -o llc LLVMSelectionDAG.o If I remove one of

Hello, Reid. You wrote Tuesday, May 16, 2006, 11:13:19 PM: RS> What does the assertion say? The same text, as in the original e-mail: <=cut=> /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: BFD 2.16.91 20050610 assertion fail /netrel/src/binutils-20050610-1/bfd/cofflink.c:1926 <=cut=> This assertions is in big function named: bfd_boolean

Hello, Chuck. You wrote Tuesday, May 16, 2006, 6:03:14 PM: C> I shall skip llc and have another try. The cheap workaround is to use .a files instead of relinked .o. If you want, I can send patch. -- With best regards, Anton mailto:asl at math.spbu.ru Thursday, May 18, 2006 7:22:54 PM Faculty of Mathematics & Mechanics, Saint-Petersburg State University

Hello, Jon The main idea of llvm-gcc is to be a drop-in replacement of gcc. So, if you know how to install & run gcc on your system, you should be able to do the same with llvm-gcc (thus no "Getting Started" entry). Basically the only "packaging differences" wrt normal gcc is that we're shipping w32api & mingw-runtime packages with llvm-gcc. Surely, you still need

I've just got flac-1.0.4 to successfully compile under my MinGW environment: MinGW-2.0.0-3 - binutils-2.13.90-20021006-2 - w32api-2.1 MSYS-1.0.8-rc4 This is on an AMD Athlon machine with 512MB RAM running Windows XP. The only change I had to make was to include/FLAC/ordinals.h.in to remove the reference to MINGW32 on line 39 - without this change the compile bailed out very early on.

I successfully built llvm using msys/mingw, but I am getting the following error when I try to build llvm-gcc using $ ../llvm-gcc4.2-2.6.source/configure --prefix=/c/Temp/msys-llvm-gcc --program- prefix=llvm- --enable-llvm=/c/Temp/msys-llvm --enable-languages=c,c++ --disable -shared $make -------------------------------------------------- gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings

> The main idea of llvm-gcc is to be a drop-in replacement of gcc. So, > if you know how to install & run gcc on your system, you should be > able to do the same with llvm-gcc (thus no "Getting Started" entry). > Basically the only "packaging differences" wrt normal gcc is that > we're shipping w32api & mingw-runtime packages with llvm-gcc. Surely,

Hello, Oscar. You wrote Sunday, April 23, 2006, 8:31:14 PM: OF> Forward works ok with MinGW. Back slashes can be interpreted as escape OF> sequences by MSYS/Cygwin tools. I've succeeded in building CFE in Mingw at some 1.3-1.4 release. After, I just don't have enough time to play with LLVM. I've sent my instructions to Henrik Bach <henrik_bach_llvm at hotmail.com>, maybe

The problem with building the frontend on Windows is that gcc cannot be bootstrapped using Window's native compiler -- i.e. VC++ -- unlike every other platform. It can be built on Windows using gcc, of course, but even then only if the entire GNU environment is present. The real problem is that the bootstrapped frontend binaries built using gcc may not properly link with LLVM binaries built

Hi, I'm able to build the llvm tools on the MinGW platform: burg, fpcmp, tblgen, llvm-as, llvm-dis, opt, gccas, llc, llvm-link, lli, gccld, llvm-stub, analyze and extract. I wonder if these tools are sufficient to start build the cfrontend? Henrik. _________________________________________________________________ Undg� pop-ups med MSN Toolbar - http://toolbar.msn.dk hent den gratis!

On Tue, 2 Nov 2004, Jeff Cohen wrote: > The problem with building the frontend on Windows is that gcc cannot be > bootstrapped using Window's native compiler -- i.e. VC++ -- unlike every > other platform. It can be built on Windows using gcc, of course, but > even then only if the entire GNU environment is present. Yeah, annoying. Unfortunately we're not up to fixing GCC :)