#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:149 dimpase]:
 > few things about Cygwin rebase/rebaseall.
 >
 >   * we should rebase .so files, too;
 I think you should go even further and only have *.dll files.
 >   * {{{rebase}}} has a new handy -O switch, which means rebase (new)
 things, but do not touch the system dlls. So instead of rebaseall,
 assuming one installs Sage on a system without previous versions of Sage
 installed, one can do, at the Cygwin shell (no need to kill all the Cygwin
 processes, as is the case for rebaseall):
 > {{{
 > $ cd $SAGE_ROOT
 > $ find . -name *.dll >/tmp/list_of_files
 > $ find . -name *.so >>/tmp/list_of_files
 > $ rebase -O -T /tmp/list_of_files
 > }}}
 Good to know, thanks for the hint!
 I finally get rid of the BLODA which memleak on my 64 bis W7 (that was the
 Lenovo FastBoot thing, not even sure what it does, except keeping 20K of
 memory in page table for every app ever launched, Cygwin or not...).
 >   * previous versions of Sage clog up the limited static dll address
 space maintained by Cygwin in {{{/etc/rebase*}}} databases. I recommend to
 wipe them out before installing the new version of Sage; i.e. remove Sage
 installation(s) and {{{/etc/rebase*}}} and run rebaseall as usual, in
 {{{ash}}} or {{{dash}}}.
 Yup, that's a good idea.

 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.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6743#comment:150>
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.


Reply via email to