I have realised that mpir is as far as I am aware the only project I have
compiled so far that uses configure. At least the only one that has caused
issues thus bringing it to my attention.
It may be an issue with msys and sh.exe although the last isssue (cannot
determine how to define a 32-bit wo
I'm afraid I haven't seen this before. If it is randomly doing this, then
there must be something wrong with the environment. Sorry I don't think I
have any specific advice.
Bill.
On 2 May 2013 14:33, gmail wrote:
>
> When attempting to configure using the latest mingw install i get the
> foll
When attempting to configure using the latest mingw install i get the
following error...
checking for assembler local label prefix... L
checking for assembler byte directive... .byte
checking how to define a 32-bit word... configure: error: cannot determine
how to define a 32-bit word
At th
I am using mingw 4.4.
I disabled virus protection
this time it froze at
configure: creating ./config.status
the config.log ends at
configure:28571: creating ./config.status
I'll try and compile it outside of the kde environment and see what happens...
DC
On 02/05/2013 9:54 PM, Bill Hart wr
Hi,
is this using Cygwin, MinGW or MSVC?
If you are getting random hangs, it could be due to an antivirus program or
an old version of MinGW.
Bill.
On 2 May 2013 12:51, developerchris wrote:
>
> The main error is a particularly odd one
>
> when using the emerge system to compile mpir on wind
The main error is a particularly odd one
when using the emerge system to compile mpir on windows xp it just hangs at
seemingly random places while configuring yasm
Sometimes it will fail complaining that python is too low a version. it
requires > 2.4 and my version is only 3.3
I am pretty sur
