2012/3/21 Christer Solskogen <christer.solsko...@gmail.com>: > On 21/3-2012 8:46 PM, Vincent Torri wrote: > >>> as Kai and I pointed out, you misconfigured by not specifying the "--build" >>> option, implicitely telling autotools you were cross-compiling, resulting in >>> it wanting a "<triplet>-ar". Nowhere in that little story did any reference >>> to any "<triple>-gcc-ar" ever pop up. Autotools doesn't even check for such >>> an executable. >> >> of course it does ! >> > > No, it does not. > >> i took one of my libs that i cross often compile. I configured it in >> MSYS by setting --host=i686-w64-mingw32 >> >> result: >> >> checking for i686-w64-mingw32-ar... no >> checking for ar... ar >> >> So it does check for i686-w64-mingw32-ar... >> > > And Ruben just told you that it does not check for i686-w64-mingw32-gcc-ar. > > Forget about *-gcc-ar already! And no, ar and gcc-ar is not the same > thing even if you want it to. > > -- > chs
There are actual more of those <triplet>-gcc-* executables. Namely <triplet>-gcc-ar.exe <triplet>-gcc-nm.exe <triplet>-gcc-ranlib.exe The are generated by plugin-feature. Simply ignore them, I don't expect that you might actaul want them to use. Kai ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
