2010/6/16 Ruben Van Boxem
> 2010/6/16 JonY
>
> On 6/16/2010 18:51, Ruben Van Boxem wrote:
>>
>>>
>>> Either way, without more of the config log it's difficult to tell why
it's trying to use a half-msvc toolchain.
>>> I have attached stderr and stdout logs for
>>> configure --host
On 6/16/2010 18:51, Ruben Van Boxem wrote:
>
>> Either way, without more of the config log it's difficult to tell why
>> it's trying to use a half-msvc toolchain.
>>
>
> I have attached stderr and stdout logs for
> configure --host=x86_64-w64-mingw32 --disable-shared --enable-alloca=no
>
the confi
2010/6/16 Mook >
> Either way, without more of the config log it's difficult to tell why
> it's trying to use a half-msvc toolchain.
>
I have attached stderr and stdout logs for
configure --host=x86_64-w64-mingw32 --disable-shared --enable-alloca=no
stderr.log
Description: Binary data
stdout.
On 2010-06-15 6:49 AM, Ruben Van Boxem wrote:
>
> That's exactly why I said MSYS is special... and I don't know what will
> break if I try to fix it. I still find it very odd that GMP configure even
> knows about the name "link", because no mingw toolchain even has such a
> thing. Shouldn't the sc
