2012/3/21 Vincent Torri <[email protected]>
> On Wed, Mar 21, 2012 at 7:22 PM, Ruben Van Boxem
> <[email protected]> wrote:
> > 2012/3/21 Vincent Torri <[email protected]>
> >>
> >> On Wed, Mar 21, 2012 at 7:10 PM, Christer Solskogen
> >> <[email protected]> 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 ?
>
No need to get snide. I read each of your emails, and even replied to most
of them. Did you read my answers?
The only concrete example of a failing project you gave, was binutils,
which 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. Ignore these new executables, because as
Xunxun already said (in mail 3 of the thread, they are related to the
GCC-binutils plugin architecture, which wasn't enabled for my build. Delete
them for all I care.
Now unless you have a problem that hasn't already been solved, please
*refrain* from *not giving* details which might actually get your unknown
problem solved.
Ruben
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
