Mark> 1. What happens if you build with the '-ffloat-store' option to
    Mark>    gcc?

Doesn't quite work:

    % ./python
    Python 3.0 (r30:67503, Dec  5 2008, 09:48:42)
    [GCC 4.2.2] on sunos5
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import cmath
    >>> cmath.exp(complex(710.0, 1.5))
    Segmentation Fault (core dumped)

:-/

    Mark> 2. It looks as though the configure script isn't finding 'isinf'
    Mark>    on Solaris 10.  Any ideas why?  Is there some replacement for
    Mark>    isinf that's spelt differently?  I suspect that if we were
    Mark>    using the system lib's test for infinity instead of the
    Mark>    Py_IS_INFINITY workaround then this problem wouldn't have come
    Mark>    up.

Thanks for the tip.  The configure script doesn't #include <math.h> so
isinf() is not mapped to __builtin_isinf().  Consequently the conftest link
fails:

    configure:21401: checking for isinf
    configure:21457: gcc -o conftest -g -O2   conftest.c -lresolv -lsocket -lnsl
    -lrt -ldl  -lm >&5
    conftest.c:252: warning: conflicting types for built-in function 'isinf'
    Undefined                        first referenced
     symbol                                                 in file
    isinf                               /var/tmp//ccmTAet6.o
    ld: fatal: Symbol referencing errors. No output written to conftest
    collect2: ld returned 1 exit status

I found this code in /usr/include/iso/math_c99.h, included by <math.h>:

    #undef      isinf
    #define     isinf(x)        __builtin_isinf(x)

Skip