This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Patch to install.texi


On Tue, 12 Jun 2001, Joseph S. Myers wrote:
> This patch improves documentation of installation directories (in
> particular).  The point is to render the information in the old
> gcc/README obsolete so it can be replaced by an even more minimal
> README at toplevel.  It passes install.texi2html and texi2dvi.  OK to
> commit to mainline and 3.0 branch?

Definitely, good work. Thanks!

Just some suggestions (from a non-native speaker, albeit, so please
take with a grain of salt):

> +@item --bindir=@var{dirname}
> +Specify the installation directory for the executables (such as
> +@command{gcc} and @command{g++}) called by users.  The default is
> +@file{@var{exec-prefix}/bin}.

...executables called by users (such as...)... ?

> +@item --libdir=@var{dirname}
> +Specify the installation directory for object code libraries and
> +internal parts of GCC.  The default is @file{@var{exec-prefix}/lib}.

...programs internally used by GCC ... ?

> +@item --infodir=@var{dirname}
> +Specify the installation directory for info documentation.  The default
> +is @file{@var{prefix}/info}.

...documentation in info format... ?

> +Specify the installation directory for manpages.  The default is
> +@file{@var{prefix}/man}.

...man pages... or, better, ...manual pages... ?

> +@command{g77} manpage is unmaintained and may be out of date; the others
> +are derived by an automatic conversion process from parts of the full
> +manual.)

s/parts of the full manual/the full manual/

As we already say "derived" this sounds better. I think?

> +@item --with-cpp-install-dir=@var{dirname}
> +Specify that the user visible @command{cpp} program should be installed
> +in @var{dirname} (relative to @var{prefix}), in addition to @var{bindir}.

How about specifying the full name @file{@var{prefix}/@var{dirname}/cpp} ?

> +in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
> +parts of the compiler in @file{@var{libdir}/gcc-lib}; info documentation
> +in @file{@var{infodir}} (normally @file{@var{prefix}/info}).

See above.

> +If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
> +dvi}.  You will need to have @command{texi2dvi} (version at least 4.0)
> +and @TeX{} installed.  This creates a number of @file{.dvi} files in
> +subdirectories of @file{@var{objdir}}; these may be converted for
> +printing with such programs as @command{dvips}.

...programms such as... or ...programs like...?

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]