#6743: cygwin metaticket: port Sage to Microsoft Windows (via Cygwin): stage 1 
--
make building Sage automatic
-------------------------------+--------------------------------------------
       Reporter:  was          |         Owner:  was     
           Type:  enhancement  |        Status:  new     
       Priority:  major        |     Milestone:  sage-5.6
      Component:  cygwin       |    Resolution:          
       Keywords:  sd31 sd32    |   Work issues:          
Report Upstream:  N/A          |     Reviewers:          
        Authors:               |     Merged in:          
   Dependencies:               |      Stopgaps:          
-------------------------------+--------------------------------------------
Description changed by kcrisman:

Old description:

> The goal of this ticket is that a person can:
>
>    1. Install Cygwin and certain standard Cygwin packages (listed below).
>
>    2. Extract the Sage tarball and type "`make`"
>
> and have everything build automatically with no errors.   The goal is
> '''not''' that the resulting build works or Sage starts up.  That will be
> for a later ticket.  Adding checks for all these prereqs will also be
> part of a future ticket.
>
> ----
>
> == Most recent trials and a lot more status detail is at
> http://trac.sagemath.org/sage_trac/wiki/CygwinPort  ==
>
> == Current instructions (work on Windows XP and Windows 7 with latest
> Cygwin) ==
>
>  * As below with 5.5.rc0
>  * You will have to add patches for #13325 (which is there) and #13802
> (no patch yet)
>
> === Cygwin prereqs ===
>  * Be sure to install `file`, `liblapack`, `liblapack0`, `liblapack-
> devel`.
>  * Also need `libiconv` and `openssl` and `openssl-devel`.
>  * Might as well install `libgc-devel` - although it's not needed to
> build, it probably is to start.
>  * Since we will go with #11232, install `patch`.
>  * On Windows 7 (or both) install `libncurses-devel`.
>  * Don't forget `fortran`.
>  * Make sure you download all `gcc` and `g++` so the versions match (in
> this case, gcc4 is the type we want).
>  * We also need make and perl
>  * m4 is currently needed because of the prereq script, but once #12112
> is closed, it won't be.
>  * Just to make sure, avoid building in home directories of Windows
> domain users, as they are treated in a special way by Windows (and
> Cygwin). Probably also it's a good idea that all the pathnames do not
> contain capital letters (Windows is case-insensitive in this way, unlike
> Unices), spaces, etc.
>  * Similarly, do not ''test'' without making sure that `SAGE_TESTDIR`
> does not contain spaces.
>  * Also, '''don't forget to''' {{{export SAGE_PORT=yes}}}!
>
> === Spkgs ===
>
>  * #11635 (NTL)
>  * #13324 (ECL, but *not* including #9167 yet)
>  * #13137 (MPIR)
>  * #13755 (linbox, on Win 7)
>  * #13325 (eclib)
>  * #13319 (Python, based on #13631)
>  * #13799 (cvxopt, on XP - no spkg available yet, may have to `touch
> spkg/installed/cvxopt-1.1.5` manually if it fails)
>
> This should then work 'out of the box', modulo rebasing issues (see
> [wiki:CygwinPort]).  See [wiki:CygwinPort the wiki] for other details as
> well.
>
> ----
>
> Much older info, archived:
>
> I have put a binary of my Cygwin build here:
>
> http://sage.math.washington.edu/home/wstein/tmp/sage-4.1-cygwin-i686-CYGWIN_NT-5.1.tar.gz
>
> Things like "`sage -ipython`" and many non-Sage imports work.  Just
> starting Sage doesn't, maybe because of the Sage<-->pynac binding not
> building.
>
> Required Cygwin packages beyond the usual:
>
>    * GCC 4.3.2
>    * `gfortran`
>    * `libncurses-devel`
>    * `lapack`
>    * `openssl-devel`
>    * `libiconv` -- needed when building R (and it has to be `libiconv`)
>
> We need to add a test for '''all''' of the above to the prereq script
> before making the Cygwin port official.

New description:

 The goal of this ticket is that a person can:

    1. Install Cygwin and certain standard Cygwin packages (listed below).

    2. Extract the Sage tarball and type "`make`"

 and have everything build automatically with no errors.   The goal is
 '''not''' that the resulting build works or Sage starts up.  That will be
 for a later ticket.  Adding checks for all these prereqs will also be part
 of a future ticket.

 ----

 == Most recent trials and a lot more status detail is at
 http://trac.sagemath.org/sage_trac/wiki/CygwinPort  ==

 == Current instructions (work on Windows XP and Windows 7 with latest
 Cygwin) ==

  * As below with 5.5.rc0
  * You will have to add patches for #13325 and #13802 during the build of
 the Sage library.  Once it fails, do (assuming you are in `SAGE_ROOT`)
 {{{
 ./sage -sh
 cd devel/sage
 <import the patches - you may need to make ~/.hgrc>
 cd ../..
 ./sage -b
 <assuming all goes well here>
 touch spkg/installed/sage-5.5.rc0 # or whatever the version number is
 exit
 }}}
   which will bring you back to your normal shell.

 === Cygwin prereqs ===
  * Be sure to install `file`, `liblapack`, `liblapack0`, `liblapack-
 devel`.
  * Also need `libiconv` and `openssl` and `openssl-devel`.
  * Might as well install `libgc-devel` - although it's not needed to
 build, it probably is to start.
  * Since we will go with #11232, install `patch`.
  * On Windows 7 (or both) install `libncurses-devel`.
  * Don't forget `fortran`.
  * Make sure you download all `gcc` and `g++` so the versions match (in
 this case, gcc4 is the type we want).
  * We also need make and perl
  * m4 is currently needed because of the prereq script, but once #12112 is
 closed, it won't be.
  * Just to make sure, avoid building in home directories of Windows domain
 users, as they are treated in a special way by Windows (and Cygwin).
 Probably also it's a good idea that all the pathnames do not contain
 capital letters (Windows is case-insensitive in this way, unlike Unices),
 spaces, etc.
  * Similarly, do not ''test'' without making sure that `SAGE_TESTDIR` does
 not contain spaces.
  * Also, '''don't forget to''' {{{export SAGE_PORT=yes}}}!

 === Spkgs ===

  * #11635 (NTL)
  * #13324 (ECL, but *not* including #9167 yet)
  * #13137 (MPIR)
  * #13755 (linbox, on Win 7)
  * #13325 (eclib)
  * #13319 (Python, based on #13631)
  * #13799 (cvxopt, on XP - no spkg available yet, may have to `touch
 spkg/installed/cvxopt-1.1.5` manually if it fails)

 This should then work 'out of the box', modulo rebasing issues (see
 [wiki:CygwinPort]).  See [wiki:CygwinPort the wiki] for other details as
 well.

 ----

 Much older info, archived:

 I have put a binary of my Cygwin build here:

 
http://sage.math.washington.edu/home/wstein/tmp/sage-4.1-cygwin-i686-CYGWIN_NT-5.1.tar.gz

 Things like "`sage -ipython`" and many non-Sage imports work.  Just
 starting Sage doesn't, maybe because of the Sage<-->pynac binding not
 building.

 Required Cygwin packages beyond the usual:

    * GCC 4.3.2
    * `gfortran`
    * `libncurses-devel`
    * `lapack`
    * `openssl-devel`
    * `libiconv` -- needed when building R (and it has to be `libiconv`)

 We need to add a test for '''all''' of the above to the prereq script
 before making the Cygwin port official.

--

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6743#comment:65>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to