Mercurial > octave-nkf
diff doc/interpreter/install.txi @ 9031:1052a66078cf
Documentation cleanup of top-level Octave directory (READMEs, INSTALL)
Spellcheck README and INSTALL files.
Start all sentences with two spaces after period for readability.
author | Rik <rdrider0-list@yahoo.com> |
---|---|
date | Thu, 19 Mar 2009 20:47:36 -0700 |
parents | eb63fbe60fab |
children | c79cf77061b7 |
line wrap: on
line diff
--- a/doc/interpreter/install.txi Sun Mar 15 12:15:50 2009 +0800 +++ b/doc/interpreter/install.txi Thu Mar 19 20:47:36 2009 -0700 @@ -34,8 +34,9 @@ Free Software Foundation. @strong{Note:} This file is automatically generated from -@file{doc/interpreter/install.txi} in the Octave sources, so to make -changes to this documentation file, change that source file. +@file{doc/interpreter/install.txi} in the Octave sources. To update +the documentation make changes to the .txi source file rather than this +derived file. @node Installation @chapter Installing Octave @@ -157,18 +158,19 @@ @item --without-framework-opengl Don't use framework OpenGL headers, libraries and specific source code -for compilation even if the configure test succeeds. If this option is +for compilation even if the configure test succeeds. If this option is given then OpenGL headers and libraries in standard system locations are -tested (the default value is @code{--with-framework-opengl}). This is a +tested (the default value is @code{--with-framework-opengl}). This is a platform specific configure option for Mac systems. @item --help Print a summary of the options recognized by the configure script. @end table -See the file @file{INSTALL} for more information about the command line -options used by configure. That file also contains instructions for -compiling in a directory other than where the source is located. +See the file @file{INSTALL} for more general information about the +command line options used by configure. That file also contains +instructions for compiling in a directory other than where the source +is located. @item Run make. @@ -184,7 +186,7 @@ any but the most peripheral sense. To compile Octave, you will need a recent version of GNU Make. You will -also need a recent version of @code{g++} or other ANSI C++ compiler. You +also need a recent version of @code{g++} or other ANSI C++ compiler. You will also need a Fortran 77 compiler or @code{f2c}. If you use @code{f2c}, you will need a script like @code{fort77} that works like a normal Fortran compiler by combining @code{f2c} with your C compiler in @@ -202,7 +204,7 @@ @url{ftp.gnu.org} is available by anonymous ftp from @url{ftp://ftp.gnu.org/pub/gnu/GNUinfo/FTP}. -You will need about 925 megabytes of disk storage to work with when +You will need about 1 gigabyte of disk storage to work with when building Octave from source (considerably less if you don't compile with debugging symbols). To do that, use the command @@ -372,7 +374,7 @@ @noindent to match the prototype declaration for the @code{signal} function. This change should also be made for the @code{SIG_DFL} and @code{SIG_ERR} -symbols. It may be necessary to change the definitions in +symbols. It may be necessary to change the definitions in @file{sys/signal.h} as well. The @code{gcc} @code{fixincludes} and @code{fixproto} scripts should