Differences between revisions 1 and 21 (spanning 20 versions)
⇤ ← Revision 1 as of 2009-07-10 20:44:56 →
Size: 1389
Editor: RalfHemmecke
Comment:
← Revision 21 as of 2010-08-20 12:34:13 → ⇥
Size: 3929
Editor: leif
Comment: Mark-ups added (commands etc.); some further fixes; reformatting. TODO: Change order of first enumeration! (*First* choose src or bin, then proceed with the [appropriate] rest.)
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Sage Download And Installation Guide = = Quick Download and Installation Guide =
Line 3: Line 3:
Not sure what [[http://www.sagemath.org/download.html|to download]]? This short guide should get you started. A [[http://wiki.sagemath.org/DownloadGuide|longer version]] of this guide is also available.
Line 4: Line 5:
 1. Determine your operating system. (Windows, Linux, Mac OS X, Solaris, etc.)  1. Determine your operating system. (Windows, Linux, MacOS X, Solaris, etc.)
Line 6: Line 7:
 1. Determine your CPU type. (32bit or [[http://www.stata.com/support/faqs/win/64bit.html|64bit]])  1. Determine your CPU type (32-bit, [[http://www.stata.com/support/faqs/win/64bit.html|64-bit]] or "atom" for Linux and [[32-64-bit-MacOS|Intel or PowerPC for MacOS]]). In case you are running a 32-bit operating system on a 64-bit CPU, choose the 32-bit version.
Line 8: Line 9:
 1. Do you want source or binary distribution?
     Usually (even if you want to do development) you will be satisfied with a precompiled version of Sage (binary release).
     The source distribution is only needed if you want to see the sources of the Sage packages, also known as [[spkg|SPKGs]].		  1. Do you want a source or binary distribution? Even if you want to do development, a precompiled version of Sage (binary release) can be used for that purpose. The source distribution is mostly needed if you want to see the sources of the Sage packages, also known as [[spkg|SPKGs]], too. Another advantage of compiling Sage from source is that the generated code may make better use of your specific CPU.
Line 14: Line 13:
 1. Follow the [[http://www.sagemath.org/doc/installation/|Installation Guide]] to actually install Sage.  1. Follow the [[http://www.sagemath.org/doc/installation/binary.html|binary installation guide]] to actually install a precompiled version of Sage. The [[http://www.sagemath.org/doc/installation/source.html|source installation guide]] contains more detailed information on compiling Sage from source.
Line 16: Line 15:
== Metalink ==
Line 17: Line 17:
== Trouble shooting == [[http://www.metalinker.org/|Metalinks]] ([[http://en.wikipedia.org/wiki/Metalink|Wikipedia]], [[http://www.freesoftwaremagazine.com/articles/using_metalinks|FSM]]) are XML files that contain multiple download sources and various checksums. Use them with a download manager below, if you want to
 * make sure that your download works properly,
 * automatically select a fast mirror,
 * recover in case of a download server failure, or
 * pause and resume a download later, or
 * check and repair a broken file.
Line 19: Line 24:
 1. If no binary version is available for you system, download the source version. Note that Sage does not compile on every system. There are various clients supporting this:
 * Cross-Platform: [[http://www.downthemall.net/|DownThemAll Firefox Extension]], [[http://jdownloader.org/|JDownloader (Java App)]]
 * Windows: [[http://www.freedownloadmanager.org/|Free Download Manager]], [[http://www.getright.com/|GetRight]], [[http://www.orbitdownloader.com/|Orbit]], ...
 * Linux: {{{sudo apt-get install aria2}}} (a command-line client)
 * MacOS X: [[http://www.yazsoft.com/|Speed Download]]
 * ... [[http://www.metalinker.org/samples.html|and many more]]
Line 21: Line 31:
 1. (((rhx: That should go to the installation guide or the error message related to sage-flags.txt should change.))) You might run into the [[http://groups.google.com/group/sage-devel/browse_thread/thread/53ae33d0324d44|following issue]] with a binary release due to different features of your system and the system on which Sage was compiled. == Troubleshooting ==

 1. If no binary version is available for your system, download the source version. Note that Sage compiles on a wide variety of systems, but does not compile on ''every'' system.

 1. If you are not sure how to unpack the compressed file or its ending looks different:
   * {{{*.tar.gz}}} or {{{*.tgz}}}: Use {{{tar xzf *.tar.gz}}}
   * {{{*.tar.bzip2}}} or {{{*.tar.bz2}}}: Use {{{tar xjf *.tar.bzip2}}}
   * {{{*.tar.lzma}}}: Use {{{tar --lzma -xf *.tar.lzma}}}
     * No {{{lzma}}}? Perhaps you have {{{xz}}}, that is compatible with {{{lzma}}}. There might also be {{{-J}}} in {{{tar -xJf *.tar.lzma}}} or you need to install an lzma or xz-utils package.
   * If the file ending is different, the Linux command {{{file}}} gives you information about the archive type. (Type {{{file filename.ext}}} at the command prompt.)

 1. You might run into the [[http://groups.google.com/group/sage-devel/browse_thread/thread/53ae33d0324d44|following issue]] with a binary release due to different features of your system and the system on which Sage was compiled.
  (((rhx: That should go to the troubleshooting section of the [[http://www.sagemath.org/doc/installation/|Installation Guide]] or (even better) the error message related to {{{sage-flags.txt}}} should change.)))

Quick Download and Installation Guide

Not sure what to download? This short guide should get you started. A longer version of this guide is also available.

  1. Determine your operating system. (Windows, Linux, MacOS X, Solaris, etc.)

  2. Determine your CPU type (32-bit, 64-bit or "atom" for Linux and Intel or PowerPC for MacOS). In case you are running a 32-bit operating system on a 64-bit CPU, choose the 32-bit version.

  3. Do you want a source or binary distribution? Even if you want to do development, a precompiled version of Sage (binary release) can be used for that purpose. The source distribution is mostly needed if you want to see the sources of the Sage packages, also known as SPKGs, too. Another advantage of compiling Sage from source is that the generated code may make better use of your specific CPU.

  4. If available, choose the appropriate binary version from one of the download mirrors.

  5. Follow the binary installation guide to actually install a precompiled version of Sage. The source installation guide contains more detailed information on compiling Sage from source.

Metalinks (Wikipedia, FSM) are XML files that contain multiple download sources and various checksums. Use them with a download manager below, if you want to

  • make sure that your download works properly,
  • automatically select a fast mirror,
  • recover in case of a download server failure, or
  • pause and resume a download later, or
  • check and repair a broken file.

There are various clients supporting this:

Troubleshooting

  1. If no binary version is available for your system, download the source version. Note that Sage compiles on a wide variety of systems, but does not compile on every system.

  2. If you are not sure how to unpack the compressed file or its ending looks different:

    • *.tar.gz or *.tgz: Use tar xzf *.tar.gz

    • *.tar.bzip2 or *.tar.bz2: Use tar xjf *.tar.bzip2

    • *.tar.lzma: Use tar --lzma -xf *.tar.lzma

      • No lzma? Perhaps you have xz, that is compatible with lzma. There might also be -J in tar -xJf *.tar.lzma or you need to install an lzma or xz-utils package.

    • If the file ending is different, the Linux command file gives you information about the archive type. (Type file filename.ext at the command prompt.)

  3. You might run into the following issue with a binary release due to different features of your system and the system on which Sage was compiled.

    • (((rhx: That should go to the troubleshooting section of the Installation Guide or (even better) the error message related to sage-flags.txt should change.)))

  4. Ask for help on the sage-support mailing list.

DownloadAndInstallationGuide (last edited 2022-04-28 19:04:21 by mkoeppe)