On 03/17/2010 11:52 PM, Nick Alexander wrote:
On 17-Mar-10, at 10:21 PM, Jason Grout wrote:
On 03/17/2010 06:41 PM, Dr. David Kirkby wrote:
What do you consider a Solaris-only issue? When a problem occurs with a
particular release only on Solaris? If that is not put on sage-devel,
you might as well say goodbye to keeping Sage building on Solaris.
William,
Can you point out a post or two that is relevant only to people using
Sage on Solaris, but is not appropriate for the sage-devel list (in
other words, can you give a specific answer to David's question
above)? If Solaris is (going to be?) a Tier 1 platform, I assume that
any breakages on the Solaris build should be reported to the main
sage-devel list, right?
I'll bite. How about the message that started this post:
David Kirkby wrote:
"""
I started a build of Sage 4.3.4.rc0 on 't2' and one of my own SPARCs.
The build on 't2' is still going but it completed on on of my SPARCs at
home. I just started to run the long doctests.
"""
So sage built, but it may or may not work. And you're building it on
another machine, but it may or not build. What was the point of this post?
Thanks for clarifying. So apparently you feel David should have waited
to post something (hopefully!) like: "Sage built on Solaris SPARC and
doctests passed." or at least "no new doctest failures happened"?
Thanks,
Jason
--
Jason Grout
--
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
