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 Microsoft security essentials
(as opposed to turning off realtime protection) I was once again able to get
to the python check
That still fails.
So microsofts antivirus is the most likely culprit although some other
service may be the cause.
I just need to track down why the python test fails
Damn! Spoke too soon. I tried running it again and it hung at creating
config.status
The file appears to hang after partially writing config.status
the next line is
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
It has to be an issue with msys/bin/sh.exe it must be failing at random
times for random reasons like returning the wrong exit code from python
Chris
On 03/05/2013 7:26 PM, [email protected] wrote:
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 that throws some light
on why the determination failed. (You need to find out why it failed.)
Search the config.log for the string "checking how to define a 32-bit
word" and read over the next few lines until you come to the actual error
message.
Cheers,
Rob
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mpir-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
