Ticket #10040: trac_10040-document_SAGE_SPKG_LIST_FILES-sage_library.patch

File trac_10040-document_SAGE_SPKG_LIST_FILES-sage_library.patch, 4.8 KB (added by leif, 9 years ago)

Apply to Sage library. Based on Sage 4.6.rc0pre1. (Updated version s.t. more people can read it.)

  • doc/en/installation/source.rst

    # HG changeset patch
    # User Leif Leonhardy <not.really@online.de>
    # Date 1287851505 -7200
    # Node ID 6afb05d16ba5714e6406fe8e89b907e400238952
    # Parent  19b47aee39c83abeb8ff779fe630e610bb48165d
    #10040 Document new environment variable SAGE_SPKG_LIST_FILES, used by sage-spkg.
    
    diff -r 19b47aee39c8 -r 6afb05d16ba5 doc/en/installation/source.rst
    a b  
    266266
    267267   This compiles Sage and all dependencies. Note that you do not need
    268268   to be logged in as root, since no files are changed outside of the
    269    ``sage-x.y.z`` directory (with one exception -- the ``.ipythonrc`` directory is created in
    270    your ``HOME`` directory if it doesn't exist).  This command does the usual steps for
    271    each of the packages, but puts all the results in the local build
    272    tree. This can take close to an hour on some machines. Depending on the
    273    architecture of your system (e.g., Celeron, Pentium Mobile, Pentium 4,
    274    etc.), it can take over three hours to build Sage from source.  If the
    275    build is successful, you will not see the word ERROR in the last 3-4 lines
    276    of output.
     269   ``sage-x.y.z`` directory (with one exception -- the ``.ipythonrc``
     270   directory is created in your ``HOME`` directory if it doesn't exist).
     271   This command does the usual steps for each of the packages, but puts
     272   all the results in the local build tree. This can take close to an hour
     273   on some machines. Depending on the architecture of your system (e.g.,
     274   Celeron, Pentium Mobile, Pentium 4, etc.), it can take over three hours
     275   to build Sage from source. If the build is successful, you will not see
     276   the word ERROR in the last 3-4 lines of output.
    277277
    278278       The directory where you built Sage is NOT hardcoded. You should
    279279       be able to safely move or rename that directory. (It's a bug if
     
    516516  OS X on a 64-bit machine, then Sage will automatically build a
    517517  64-bit binary, so this variable does not need setting.
    518518
     519- :envvar:`CFLAG64` - default value "-m64".  If Sage detects that it
     520  should build a 64-bit binary, then it uses this flag when compiling
     521  C code.  Modify it if necessary for your system and C compiler.
     522  This should not be necessary on most systems -- this flag will
     523  typically be set automatically, based on the setting of
     524  :envvar:`SAGE64`, for example.
     525
    519526- :envvar:`SAGE_FORTRAN` - see above, the "Fortran" section.
    520527
    521528- :envvar:`SAGE_FORTRAN_LIB` - see above, the "Fortran" section.
     
    525532  debugging is turned on.  If it is set to anything else, then
    526533  debugging is turned off.
    527534
     535- :envvar:`SAGE_SPKG_LIST_FILES` - Set this to "yes" to enable
     536  verbose extraction of tar files, i.e. Sage's spkg files. Since
     537  some spkgs contain a huge number of files s.t. the log files
     538  get very large and harder to search (and listing the contained
     539  files is usually less valuable), we decided to turn this off
     540  by default. This variable affects builds of Sage with ``make``
     541  (and ``sage -upgrade``) as well as the manual installation of
     542  individual spkgs with e.g. ``sage -i``.
     543
    528544- :envvar:`SAGE_FAT_BINARY` - to prepare a binary distribution that
    529545  will run on the widest range of target machines, set this variable
    530546  to "yes" before building Sage::
     
    563579  on working with gcc 3.4.x, you will have to modify some source code
    564580  to get things to work.
    565581
    566 - :envvar:`CFLAG64` - default value "-m64".  If Sage detects that it
    567   should build a 64-bit binary, then it uses this flag when compiling
    568   C code.  Modify it if necessary for your system and C compiler.
    569   This should not be necessary on most systems -- this flag will
    570   typically be set automatically, based on the setting of
    571   :envvar:`SAGE64`, for example.
    572582
    573583Environment variables dealing with specific Sage packages:
    574584
  • doc/en/installation/source.rst

    # HG changeset patch
    # User Leif Leonhardy <not.really@online.de>
    # Date 1287861324 -7200
    # Node ID 21f1c6b81e4a0331e94c7c27d613e458b0d66b86
    # Parent  6afb05d16ba5714e6406fe8e89b907e400238952
    #10040 Expand abbreviation s.t. it's more readable to non-mathematicians and alike.
    
    diff -r 6afb05d16ba5 -r 21f1c6b81e4a doc/en/installation/source.rst
    a b  
    534534
    535535- :envvar:`SAGE_SPKG_LIST_FILES` - Set this to "yes" to enable
    536536  verbose extraction of tar files, i.e. Sage's spkg files. Since
    537   some spkgs contain a huge number of files s.t. the log files
     537  some spkgs contain a huge number of files such that the log files
    538538  get very large and harder to search (and listing the contained
    539539  files is usually less valuable), we decided to turn this off
    540540  by default. This variable affects builds of Sage with ``make``