From: Kai T. <kti...@go...> - 2012-03-21 21:08:00
|
2012/3/21 Vincent Torri <vin...@gm...>: > On Wed, Mar 21, 2012 at 9:28 PM, Christer Solskogen > <chr...@gm...> wrote: >> 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. > > ok, i misread that. > > Anyway, the fact that i686-w64-mingw32-ar is missing *is* a problem > > > i stop that conversation, now, it goes nowhere Ok, but please remember about the advice of using --build option here for binutils. As I assume you have instead build native ar.exe etc. Kai |