I managed to get mpir to compile.
The sh issue is either as you say a problem with msys or something peculiar
to my machine. I could get past it by locating the rogue sh process and
killing it. I am working on resolving the cause of it.
The problem with python failing the version test magicall
Either way, this just doesn't sound like an MPIR problem but a
MinGW/msys one.
You might want to ask on their list about random stalls.
On later versions of Windows you must disable all antivirus software and
run the MinGW/msys shell in administrator mode to avoid this. But to my
knowledge the la
As far as I recall there was nothing in the logs that indicated what the
error was with the 32 bit word test. it just stopped at the line that said
it was testing it. I have tried rebuilding again so the log was deleted. so
I cant be 100% sure.
By running in safe mode and totally disabling M
From: gmail
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 that point configure quits
There should be an error message in the config.log
Hi Chris,
configure is automatically generated by autotools from configure.in. There
is no need to go digging through the tests that it runs. If configure
doesn't run on your machine, then something is very wrong.
Bill.
On 3 May 2013 03:21, Chris Hamono wrote:
> I have realised that mpir is a
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
11 matches
Mail list logo
