Ah, indeed I didn't read the failure log correctly. It was mingw32.

So I really have to get that going on my system somehow.

Does anyone know where I can download a working version of Mingw32
that is easy to install and has a working gcc for Vista 32 bits?

Bill.

2009/4/9 Bill Hart <[email protected]>:
> Oh, have I got this mixed up? I assumed it was ming64 that we had the
> --enable-fat issue. It was on Windows 2000 if I recall. Could it have
> been mingw32 on Windows 2000?
>
> Bill.
>
> 2009/4/9 Cactus <[email protected]>:
>>
>>
>>
>> On Apr 9, 9:14 am, Bill Hart <[email protected]> wrote:
>>> I fixed a bug in fat.c in the x86 directory (replace athlon with k8)
>>> and on cygwin32 MPIR builds and passes make check. The fat binary also
>>> builds and passes make check.
>>>
>>> I'm going to downgrade the bug we have listed in trac for cygwin32
>>> from a blocker, as it only appears to affect old versions of Cygwin.
>>> I'm not totally sure we can do anything for such setups.
>>>
>>> As for MSYS/Mingw, I can't even get the C compiler to work on my Vista
>>> 32 machine. Thus if I can't even get the Mingw to work, there's no way
>>> I can test MPIR on it.
>>>
>>> I may get access to Vista 64 in the next week or two, so that means I
>>> may be able to test with Mingw64. That might allow us to knock the 64
>>> bit --enable-fat issue for Mingw64.
>>
>> I have used Mingw64 on Windows Vista x64 so this should be possible.
>>
>> But it is still a bit of a problem because the GCC compiler itself
>> depends on GMP and the official version of GMP dooesn't work on
>> Windows x64 (at least it didn't when I last looked at this).
>>
>>  Brian
>>
>> >>
>>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to