Hi,
I’m trying to build llvm and clang on windows using mingw/msys with the compilers provided be the llvm-gcc 2.7 release.
On a first not I had to rename the i386-mingw32-… stuff to gcc, g++ and so on to passify configure about the compilers.
I configure with --enable-jit --disable-threads and --with-llvm-gccdir=…
Now I keep getting warnings about the “–export-dynamic” flag which is unsupported. Now the question is should I change it to “–export-all-symbols” as suggested?
-Frank
Update (soory for posting twice): building with the provided compilers in the mentioned configuration fails with the error:
“Memory exhausted” while building libLLVMAsmPrinter.a
2010/7/21 Frank Fuchs <fk.fuchs@googlemail.com>
Hello
Update (soory for posting twice): building with the provided compilers in
the mentioned configuration fails with the error:
"Memory exhausted" while building libLLVMAsmPrinter.a
Well, it seems that:
- Either your compiler / linker is buggy
- You indeed have too few memory for this
ok insufficient RAM can be denied 
concerning the compiler ... it was the llvm-gcc 2.7 release.
May be the linker, because there I used the MSys provided one.
In the meanwhile I compiled llvm+clang sucessfully (with --export-all-symbols), using the "sezero" build of mingw.
I trust this compiler quite a lot since I used it successfully for Qt4.7beta and boost.
However I need to test my build before declaring victory.
Now any comments about export-all-symbols?
-Frank
Ok after some small “Hello world” tests clang and clang++ seem to work, now. (compiled using mingw32_sezero and --export-all-symbols). However, for linking the a clang++ compiled executable I need to pass the -fno-use-cxa-atexit flag, as mentioned here [http://llvm.org/bugs/show_bug.cgi?id=7276]. Maybe someone could eliminate these two annoyances by patching configure and Tools.cpp in trunk?
-Frank
2010/7/21 Frank Fuchs <fk.fuchs@googlemail.com>