Robert Miller wrote:
David,
I don't know how important #6583 it so Sage, or how important William
sees a Solaris port as important, but at the minute, these two appear to be
mutually exclusive.
I don't know if I agree with that. Have you tried tinkering with the
build flags on t2? We had several different suggestions of
modifications to make to the build flags, e.g. for ratpoints... Have
any of these been tested yet?
I have put some comments on the trac ticket
http://trac.sagemath.org/sage_trac/ticket/6583
but in essence, I've tried building ratpoints with
* -D_XOPEN_SOURCE=600
* -std=c99
* -std=c99 -D_XOPEN_SOURCE=600
Ratpoints will build with any of these, but the sage library does not build
properly. I've not tried building the library with -D_XOPEN_SOURCE=600, as I
don't know how to do that. Perhaps you could try that option in your code if it
seems appropriate, though it is cython which is generating the C, so maybe that
is not so easy.
As a minor issue, ratpoints currently builds with -DUSE_SSE on any platform
except OS X, which is a bit silly on SPARC, as there are no SSE instructions.
But even building without that, just as is done on OS X, does not help the
situation. I'm somewhat surprised ratpoints builds while trying to use SSE
instructions, but it seems to.
Is there any chance you could make your code which mixes with ratpoints
http://trac.sagemath.org/sage_trac/ticket/6583
as an experimental package, until such time as this issue can be resolved?
Because at the minute, #6583 totally screws up attempts to build on Solaris 10
(SPARC) where Sage did work, and makes it very difficult to make progress on
OpenSolaris.
Dave
--
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
