On 08/ 2/10 12:18 AM, William Stein wrote:
On Fri, Jul 30, 2010 at 3:52 PM, Dr. David Kirkby
<david.kir...@onetel.net> wrote:
On 07/30/10 11:08 PM, William Stein wrote:
Obviously, a Cygwin windows port of Sage would be much better. It's
too bad nobody is working on that at all either.
William
I thought you and Mike Hansen were working on that, and expected to have it
done for Sage 5.0 next month.
I'm afraid neither of us has worked on it in about 2 months. Mike
just moved and I was busy with numerous Sage Days workshops. I will
also personally have little time to work on it for the rest of this
summer. Nobody else has worked on port yet.
I might be persuaded to have a look at that once I get all the Solaris ports
done.
That would be awesome.
64-bit OpenSolaris is my main aim, but I'd like to get Sage building
on fulvia (Solaris 10 x86) as well as 64-bit SPARC. Fortunately, 95% of the
issues affecting one Solaris platform affect another, so they are likely to
come together.
Is there available a detailed document about how to set up Cygwin,
Yes -- http://cygwin.com
what's needed to install Sage, then a list of the issues?
There is this page
http://trac.sagemath.org/sage_trac/wiki/CygwinPort
the contents of the sage-windows mailing list
http://groups.google.com/group/sage-windows
and nothing else.
Does Sage actually compile on Cygwin, but just not run well (which is the
case with 64-bit SPARC), or does it simply not build at all?
It's more complicated than that. It does not fully build, but if one
swaps out a few spkg's for slightly modified versions then it *does*
fully build. Moreover it runs and passes most of the test suite.
This page (http://trac.sagemath.org/sage_trac/wiki/CygwinPort) lists
the 13 tickets I made for doctest failures -- I think they are nearly
comprehensive.
I've made a few comments on some of the trac tickets you list at
http://trac.sagemath.org/sage_trac/wiki/CygwinPort
There's a chance #9170 might be a trivial fix. There's no code in
devel/sage-main/sage/misc/getusage.py to attempt to get memory usage on Cygwin
at all. Even if 'top' did exist, it would not be called. But you have the option
of trying the code which is used on Linux. I don't think using 'top' from a
script like this is ever a good idea myself.
ECL generates a couple of rather serious looking compiler warnings to me. They
could possibly be the cause of #9167.
lcalc generates a lot of compiler warnings. Perhaps something in there might
result in the problems seen with that.
Pynac will not compiler with SunStudio or MSCV. I'd look at what those compilers
object to.
Anyway, I left comments on the trac tickets in most cases.
Dave
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
