Hi all,

my efforts building Python 2.4.1 on Solaris 10(x386)
failed.

The error mesage reads:
(...)Objects/complexobject.c: In function `complex_pow':
Objects/complexobject.c:479: error: invalid operands to
binary ==
Objects/complexobject.c:479: error: wrong type argument
to unary minus
Objects/complexobject.c:479: error: invalid operands to
binary ==
Objects/complexobject.c:479: error: wrong type argument
to unary minus
*** Error code 1
make: Fatal error: Command failed for target
`Objects/complexobject.o'

I found bug 970334 dealing with that topic, but I
didn't find a solution provided.

I tried with various compilers and libraries, e.g.
/opt/sfw/bin/gcc --version
gcc (GCC) 3.4.2
Copyright (C) 2004 Free Software Foundation, Inc.
/opt/csw/gcc3/bin/gcc --version
gcc (GCC) 3.4.4
Copyright (C) 2004 Free Software Foundation, Inc.
/usr/local/bin/gcc --version
gcc (GCC) 3.3.2

The same result with any of them.

I didn't get the solution provided in
http://mail.python.org/pipermail/python-list/2005-August/293795.html
to work for me, unfortunately.

I'd be glad, if you could have a look into this issue.

Thanks in advance,
Chris

Logged In: YES 
user_id=1188172

Looks like HUGE_VAL is defined in a curious way on your
platform. Can you find out what header defines HUGE_VAL and
to what it expands?

Logged In: YES 
user_id=1337267

Hi all,

I found a newsgroup posting which adviced to change a line
in Include/pyport.h

http://mail.python.org/pipermail/patches/2005-February/016881.html

---------------8<-----------------------------------------------------
The fix I used was to make the following change in
pyport.h:

Change
#define Py_HUGE_VAL HUGE_VAL

to

#define Py_HUGE_VAL DBL_MAX.

DBL_MAX is found in float.h
--------------->8-----------------------------------------------------

I did as adviced and the compile worked. I am not sure, if
this is a valid solution, but at least it´s a workaround.

Thanks to  Reinhold Birkenfeld for your hint!

Regards,
Chris

Logged In: YES 
user_id=6606

This is a duplicate of issue #970334, which I just submitted
a patch to python-dev for.

Will close as won't fix if nobody object.

From pymath.h:

/* HUGE_VAL is supposed to expand to a positive double infinity.  Python
 * uses Py_HUGE_VAL instead because some platforms are broken in this
 * respect.  We used to embed code in pyport.h to try to worm around that,
 * but different platforms are broken in conflicting ways.  If you're on
 * a platform where HUGE_VAL is defined incorrectly, fiddle your Python
 * config to #define Py_HUGE_VAL to something that works on your platform.
 */
#ifndef Py_HUGE_VAL
#define Py_HUGE_VAL HUGE_VAL
#endif

Closing on lack of response. This issue is also addressed in pymath.h's
comments.