> Also, it would be really nice if an official > cygwin build (the binary) was published too. I spent quite a bit of > time screwing with it a few months ago, and it was quite a bastard to > get going...I had quite a time with it too, could only get the debug version to build as there seemed to be an internal problem with ld. I would very interested in how you got it running and what GCC tool versions you used ?> IMHO, it would be the easiest way to get some windows user playing > with llvm :)Yes, but it is still limited. Aaron
Hello Aaron, Aaron Gray wrote on 14/10/2005 at 5:50 a.m.:>> Also, it would be really nice if an official cygwin build (the >> binary) was published too. I spent quite a bit of time screwing >> with it a few months ago, and it was quite a bastard to get >> going... > I had quite a time with it too, could only get the debug version to > build as there seemed to be an internal problem with ld. > > I would very interested in how you got it running and what GCC tool > versions you used ?OK, I've just tried building the current CVS/HEAD on cygwin using gcc (GCC) 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125): - llvm/make tools-only worked ok - llvm-gcc/make all failed with the following message (2nd try): make[2]: Leaving directory `/home/oleg.smolsky/llvm-gcc-build/gcc' make[1]: Leaving directory `/home/oleg.smolsky/llvm-gcc-build/gcc' Checking multilib configuration... multilib.out is unchanged Configuring in i686-pc-cygwin/libstdc++-v3 configure: loading cache ../config.cache checking build system type... i686-pc-cygwin checking host system type... i686-pc-cygwin checking target system type... i686-pc-cygwin checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i686-pc-cygwin-gcc... /home/oleg.smolsky/llvm-gcc-build/gcc/xgcc - B/home/oleg.smolsky/llvm-gcc-build/gcc/ -B/pacific/llvm-gcc/i686-pc-cygwin/bin/ -B/pacific/llvm-gcc/i686-pc-cygwin/lib/ -isystem /pacific/llvm-gcc/i686-pc-cygwi n/include -isystem /pacific/llvm-gcc/i686-pc-cygwin/sys-include checking for C compiler default output... conftest.exe checking whether the C compiler works... configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. make: *** [configure-target-libstdc++-v3] Error 1 Best regards, Oleg.
Oleg,> - llvm/make tools-only worked okGood.> - llvm-gcc/make all failed with the following message (2nd try): > make[2]: Leaving directory `/home/oleg.smolsky/llvm-gcc-build/gcc' > make[1]: Leaving directory `/home/oleg.smolsky/llvm-gcc-build/gcc' > Checking multilib configuration... > multilib.out is unchanged > Configuring in i686-pc-cygwin/libstdc++-v3 > configure: loading cache ../config.cache > checking build system type... i686-pc-cygwin > checking host system type... i686-pc-cygwin > checking target system type... i686-pc-cygwin > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking for i686-pc-cygwin-gcc... > /home/oleg.smolsky/llvm-gcc-build/gcc/xgcc - > B/home/oleg.smolsky/llvm-gcc-build/gcc/ -B/pacific/llvm-gcc/i686-pc-cygwin/bin/ > -B/pacific/llvm-gcc/i686-pc-cygwin/lib/ -isystem > /pacific/llvm-gcc/i686-pc-cygwi > n/include -isystem /pacific/llvm-gcc/i686-pc-cygwin/sys-include > checking for C compiler default output... conftest.exe > checking whether the C compiler works... configure: error: cannot run C > compiled > programs. > If you meant to cross compile, use `--host'. > See `config.log' for more details. > make: *** [configure-target-libstdc++-v3] Error 1I am not sure but it looks like a problem with your Cygwin instillation ? Try a 'make configure' or 'make reconfigure'. Here's a link to the instructions I developed for building LLVM on Cygwin :- http://angray.members.beeb.net/llvm/MakingLLVM.html As far as I know it should hopefully still be correct for the debug build. It failed on the release build though due to a bug in ld, which hopefully will be fixed with time. Aaron