On Feb 13, 6:10 pm, Dima Pasechnik <dimp...@gmail.com> wrote:
.....
>
> GMP and MPFR is only a small part of the story. There are huge packages
> in Sage (not developed by Sage people) that do not run natively under
> Windows and are quite non-trivial to port (as they might have their own
> tricky GC, use fork and its POSIX-only friends, original developers of
> these parts left long ago, etc). E.g. GAP alone is a nontrivial task to
> port.
>
> > (RJF) This is not a problem if you drop the requirement that every recipient
> > of Sage must be able to COMPILE stuff locally.  Just have one person
> > compile the stuff once and distribute dll files.
>
> this means distributing a seriously crippled system.

How so?
Does that mean that only those people who compile Sage themselves
have a non-crippled system?


If Sage/linux has adopted large subsystems that do not run in windows,
then
those systems can be dropped from the Sage/windows distribution.
Report the
problem as a bug to the author(s) of such systems. When they are fixed
so they can be compiled and run in windows, put them into the windows
distribution.  Problem solved.

If you are saying that your home-grown core python Sage stuff cannot
be run in
Windows, then shame on you for turning your back on what is still the
most wide-spread operating system (or family of systems) on home
and office computers.

RJF



>
>
>
>
>
>
>
>
>
> >  I suppose
> > it is possible that some Sage propeller-heads have written python or C
> > code that cannot be compiled under windows, but it seems to me more
> > likely that it is a question of finding a skilled person, and not so
> > much of problematical code.  A skilled person who cares to look at
> > code base, and has a spare week or two.
>
> >> I must admit, I would have thought a Cygwin port easier than it seems to 
> >> be. I
> >> recall at one time wondering whether the Solaris or Cygwin port would be
> >> completed first, but Solaris got there several years ago, and the Cgywin 
> >> port
> >> seems less likely to be completed now than it did a few years ago.
>
> >> Microsoft were at some time funding a Windoze port of Sage, but I believe 
> >> the
> >> amount of funding they gave was far too small to make the slightest dent 
> >> in the
> >> problem.
>
> > Money misspent on unskilled labor, perhaps.
>
> > Incidentally, I am by no means suggesting that I have the needed
> > skills.
> > (I think I can identify someone who could do it, however.)
>
> > RJF
>
> >> 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

Reply via email to