search for: __crt_inline

...tubs.o):(.text+0x160): multiple definition of `_powf' /home/foad/llvm/objdir-mingw/Debug/lib/libLLVMCodeGen.a(RegAllocLinearScan.o):/usr/lib/gcc/i586-mingw32msvc/4.2.1-sjlj/../../../../i586-mingw32msvc/include/math.h:576: first defined here collect2: ld returned 1 exit status math.h:576 says: __CRT_INLINE float __cdecl powf (float x, float y) {return (float) pow (x, y);} The definition of _powf in RegAllocLinearScan.o seems to be marked with some LINK_ONCE_DISCARD and COMDAT stuff, so I assume multiple such definitions shouldn't cause linker errors. I don't know what libstdc++'s stub...

I'm trying to cross-compile LLVM with build=, host=target=. I'm using the following packages from Debian lenny: mingw32 4.2.1.dfsg-1 mingw32-binutils 2.18.50-20080109-1 mingw32-runtime 3.13-1 The first problem I hit was when I configured with CC, CXX, AR and RANLIB set to mingw cross-tools, but forgot to specify NM as well. This resulted in a load of warnings that scrolled off the

Oh, I forgot to mention that besides setting AR, RANLIB and the stack probing fix, you also need a very up to date binutils. 2.25 was out in december. Even with that , if you linker's default is not what you are compiling for (i.e. a multiarch toolchain), you need to set GNUTARGET also, i.e. -m32/-m64 is not enough. Some fix to autodetect non-default targets went in after christmas before the