[ python-Bugs-970334 ] 2.3.4 fails build on solaris 10 -
complexobject.c
SourceForge.net
noreply at sourceforge.net
Mon Aug 23 13:00:36 CEST 2004
Bugs item #970334, was opened at 2004-06-10 13:46
Message generated for change (Comment added) made by mwh
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=970334&group_id=5470
Category: Build
Group: Platform-specific
>Status: Closed
Resolution: None
Priority: 5
Submitted By: JD Bronson (lonebandit)
Assigned to: Michael Hudson (mwh)
Summary: 2.3.4 fails build on solaris 10 - complexobject.c
Initial Comment:
this has been an ongoing issue:
gcc -c -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -
Wstrict-prototypes -I. -I./Include -DPy_BUILD_CORE -o
Objects/classobject.o Objects/classobject.c
gcc -c -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -
Wstrict-prototypes -I. -I./Include -DPy_BUILD_CORE -o
Objects/cobject.o Objects/cobject.c
gcc -c -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -
Wstrict-prototypes -I. -I./Include -DPy_BUILD_CORE -o
Objects/complexobject.o Objects/complexobject.c
Objects/complexobject.c: In function `complex_pow':
Objects/complexobject.c:469: error: invalid operands to
binary ==
Objects/complexobject.c:469: error: wrong type
argument to unary minus
Objects/complexobject.c:469: error: invalid operands to
binary ==
Objects/complexobject.c:469: error: wrong type
argument to unary minus
make: *** [Objects/complexobject.o] Error 1
..It fails at that point with no workaround.
Jeff
----------------------------------------------------------------------
>Comment By: Michael Hudson (mwh)
Date: 2004-08-23 12:00
Message:
Logged In: YES
user_id=6656
Closing as threatened.
----------------------------------------------------------------------
Comment By: Michael Hudson (mwh)
Date: 2004-08-07 22:43
Message:
Logged In: YES
user_id=6656
Given that this has sat here for two months without
activity, I propose closing it in another fortnight.
Assigning to me on the off-chance this makes me more likely
to remember :-)
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2004-06-10 16:08
Message:
Logged In: YES
user_id=31435
See comments about Py_HUGE_VAL in pyport.h. Possible
that this platform defines C's HUGE_VAL incorrectly, in which
case config for this platfrom needs to set Py_HUGE_VAL to a
correct expansion.
You could also try compiling complexobject.c without
optimization. In at least one prior case, the platform
HUGE_VAL was correct, but expanded to such a hairy
expression that it confused the platform C compiler when
optimization was cranked up.
Finally, you didn't say which version of gcc and its libraries
you're using. It's possible that another version would work.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=970334&group_id=5470
More information about the Python-bugs-list
mailing list