#6743: cygwin metaticket: port Sage to Microsoft Windows (via Cygwin): stage 1
--
make building Sage automatic
-------------------------------+--------------------------------------------
Reporter: was | Owner: was
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-5.7
Component: cygwin | Resolution:
Keywords: sd31 sd32 | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-------------------------------+--------------------------------------------
Comment (by jpflori):
Replying to [comment:152 dimpase]:
> Replying to [comment:150 jpflori]:
> > Could you provide more info, or pointers, on why Cygwin running on a
native 32 bits system would have more address space available than one
running under wow64 on 64 bits, and so less affected by fork errors, one
as I seem to remember you evoked that at some point here?
> > I would be interested.
>
> no, my conviction was that it's not possible to have a full install of
Cygwin and a Sage on a 32-bit system, they just don't fit in that addess
space - which is bigger on wow64 on 64 bits. You are welcome to prove me
wrong. Perhaps it was some BLODA on that system I no longer have, anyway.
Hum, I got less problems with my 32bits W7 (although it was slower and had
less cores) than with my 64bits W7.
Indeed, I got fork errors in the end on the 64 bits install and not on the
32 bits install.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6743#comment:153>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
