Mike Hansen wrote:
On Wed, Feb 24, 2010 at 2:05 PM, Jaap Spies<j.sp...@hccnet.nl> wrote:
There seems to be a lot of issues with _XOPEN_SOURCE and Solaris, see:
http://bugs.python.org/issue1759169
From this discussion, it seems that we should strip out
_XOPEN_SOURCE_EXTENDED
_XOPEN_SOURCE
_POSIX_C_SOURCE
when building Python on Solaris. In that discussion, there's a patch
to configure.in or a couple of Perl commands. It seems like this
would be a good thing to try.
That's what Sun does in building python.
There is a related problem when building extensions for python
building c++ extensions we need #define _XOPEN_SOURCE_EXTENTED 0,
but building c extensions we need #define _XOPEN_SOURCE_EXTENTED 1
This is what I found on Open Solaris.
Jaap
--Mike
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
