On Wed, Mar 21, 2012 at 7:22 PM, Ruben Van Boxem <vanboxem.ru...@gmail.com> wrote: > 2012/3/21 Vincent Torri <vincent.to...@gmail.com> >> >> On Wed, Mar 21, 2012 at 7:10 PM, Christer Solskogen >> <christer.solsko...@gmail.com> wrote: >> > On 21/3-2012 5:45 PM, Vincent Torri wrote: >> > >> >> then that's problematic... There is a tool that I don't know what it >> >> does, and setting host will result in failing because of a missing >> >> ***-ar.exe >> >> >> > >> > But that's most probably your fault. You have configured binutils wrong, >> > or you don't have binutils at all. If configured and installed correctly >> > you will have ar(or ar.exe) or x86_64-w64-mingw32-ar(if you have >> > installed a cross-binutils). >> >> No, not my fault. I've always used both automatic build and Ruben's >> build before his last release. It always worked fine. >> >> I used the last one, boum error. > > > What tool are you talking about, what build system is failing, etc..? You're > not giving us anything to work with here. If you give details, preferably > stuff I/we can try to reproduce, I/we could help you. The fact remains that > your story does not make any sense, and I think an unexpected operator error > has snuck in. (Reproducible) Details would clarify.
my original mail : "in x86_64-w64-mingw32-gcc-4.7.0-3_rubenvb.7z, ar.exe is also named x86_64-w64-mingw32-gcc-ar.exe and not x86_64-w64-mingw32-ar.exe. Is it normal ?" did you read it ? Vincent ------------------------------------------------------------------------------ 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
