Ticket #13385: trac_13385-sage-library.v2.patch

File trac_13385-sage-library.v2.patch, 3.5 KB (added by jhpalmieri, 9 years ago)
  • doc/en/installation/source.rst

    # HG changeset patch
    # User J. H. Palmieri <palmieri@math.washington.edu>
    # Date 1345600338 25200
    # Node ID f64cb417ee2eb774e091eecde391759a57da5909
    # Parent  246ed14ebb068ea5f516d1333a0911062bc02250
    Document when installation of openssl, pyopenssl are needed.
    diff --git a/doc/en/installation/source.rst b/doc/en/installation/source.rst
    a b command-line development tools must be i 
    4545  versions may or may not work.  On Solaris or OpenSolaris systems,
    4646  the Sun compiler should also work.
    4747- **make**: GNU make, version 3.80 or later
    48 - **OpenSSL with dev headers**
    4948- **m4**
    5049- **perl**: version 5.8.0 or later
    5150- **tar**: GNU tar version 1.17 or later, or BSD tar
    Recommended but not strictly required: 
    6261- **ffmpeg**
    6362- **ssh-keygen**: needed to run the notebook in secure mode
    65 .. note:: If you cannot install OpenSSL and its development headers
    66    systemwide, another option is to install the optional OpenSSL spkg
    67    into your Sage installation. Unfortunately this is not possible to
    68    do immediately after extracting the tarball, so you will need to
    69    follow the build instructions as normal, wait for the build to
    70    *fail*, then run ``sage -i openssl`` and run ``make`` again.
    7264Sage also needs a C++ compiler and a Fortran compiler.
    7365However, it contains a `GNU Compiler Collection (GCC) <http://gcc.gnu.org/>`_
    74 package, such that C, C++ and Fortran compilers will be built if needed
     66package, so C, C++ and Fortran compilers will be built if needed
    7567(you can also use the environment variable :envvar:`SAGE_INSTALL_GCC` to
    7668control whether or not to install GCC).
    7769You always need some C compiler to build GCC and its prerequisites itself.
     71.. note::
     73    Optional: Read this if you are intending to run a Sage notebook server
     74    for multiple users. For security (i.e., to run
     75    ``notebook(secure=True)``) you may wish users to access the server using
     76    the HTTPS protocol. You also may want to use OpenID for user
     77    authentication. The first of these requires you to install pyOpenSSL,
     78    and they both require OpenSSL. If you have OpenSSL and the OpenSSL
     79    development headers installed on your system, you can install
     80    pyOpenSSL by building Sage and then typing ::
     82        ./sage -i pyopenssl
     84    Note that this command requires internet access.  Alternatively, ``make
     85    ssl`` builds Sage and installs pyOpenSSL.  If you are missing either
     86    OpenSSL or OpenSSL's development headers, you can install a local copy
     87    of both into your Sage installation first. Ideally, this should be
     88    done before installing Sage; otherwise, you should at least rebuild
     89    Sage's Python, and ideally any part of Sage relying on it. So the
     90    procedure is as follows (again, with a computer connected to the
     91    internet). Starting from a fresh Sage tarball::
     93        ./sage -i patch openssl  # install patch and openssl
     94        make ssl
     96    Alternatively, if you've already built Sage::
     98        ./sage -i openssl
     99        ./sage -f python   # rebuild Python
     100        SAGE_UPGRADING=yes make ssl
     102    The third line will rebuild all parts of Sage that depend on Python;
     103    this can take a while.
    79105To check if you have ``perl`` installed, for example, type
    Special Notes 
    10201046  :ref:`installation in a multiuser environment
    10211047  <sagetex_installation_multiuser>`.
    1023   **This page was last updated in August 2012 (Sage 5.2)**
     1049  **This page was last updated in August 2012 (Sage 5.3).**