Jay wrote:
Because at some point, no released version worked on intel macs.
Long since passed and can be removed?
I don't think so, http://gmp.darwinports.com/ shows that it is still a
problem with 4.2.2. Besides, GMP's authors say that it is often a
stress test for compilers, so using more C and less assembly can be a
good thing (GCC's usage of GMP does not include manipulating really
really huge numbers).
gmp/configure is where the blame really lies, but if gcc configured gmp
"normally",
this wouldn't occur. Or, is cpu=none not so abnormal? Just that I hadn't seen
it?
It's a GMP-only thing.
Given that this is a problem because of Python's apparently broken
handling of signals, we cannot do anything about it. Complain with the
Python maintainers that they should reset the signals they ignore,
before exec-ing another program.
Paolo
