#6743: cygwin metaticket: port Sage to Microsoft Windows (via Cygwin): stage 1 
--
make building Sage automatic
-----------------------------------+----------------------------------------
       Reporter:  was              |         Owner:  was                        
                                                                       
           Type:  enhancement      |        Status:  needs_info                 
                                                                       
       Priority:  major            |     Milestone:  sage-5.9                   
                                                                       
      Component:  porting: Cygwin  |    Resolution:                             
                                                                       
       Keywords:  sd31 sd32        |   Work issues:                             
                                                                       
Report Upstream:  N/A              |     Reviewers:  Jean-Pierre Flori, Dmitrii 
Pasechnik, Karl-Dieter Crisman, Mike Hansen, William Stein, Luis Tabera
        Authors:                   |     Merged in:                             
                                                                       
   Dependencies:  #14406           |      Stopgaps:                             
                                                                       
-----------------------------------+----------------------------------------

Comment (by jpflori):

 Replying to [comment:246 kcrisman]:
 > > > So the sole remaining issue ''for this ticket'' is the check for
 mpfr-4.  What should we do about this?
 > > I think we should do nothing.
 > > The Cygwin folks seems to be working on a complete overhaul of their
 GCC packages so we can hope that quite quickly the situation will get
 better and installing "gcc4-core" will just work as it used to be and as
 it should be.
 > > It is really a Cygwin packaging issue, not a Sage one, and trusting
 the Cygwin folk will avoid us the trouble to add a prereq that will soon
 be obsolete.
 > How soon is soon?  At any rate, I think that somewhere (maybe not even
 in prereq) there should be a warning.  In principle, we want someone to be
 able to download a Sage tarball, open it in Cygwin with the required Sage
 packages for any distro, and then do "make".  Maybe with some info about
 rebasing.
 >
 > Maybe that means that we need to change the ''installation guide'' here
 instead of the prereq!  We would need to provide info about rebasing
 anyway.  What do you think of that for resolving this ticket?  Then we
 could put a {{{..NOTE}}} to warn about mpfr-4 that could easily be
 removed.
 I'd say wait, from http://cygwin.com/ml/cygwin/2013-03/msg00116.html:
 {{{
 Forget the current gcc packages, they're history.  We're about to
 upgrade to 4.7 and we anyways need another rebuild before it goes
 stable.  If we ship all the updated prereqs now, each built against the
 newest gmp, then 4.7.2-2 can be built against them and we won't have
 this problem from here on out.
 }}}
 You could argue that you only trust what you see.

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