install.texi (*-*-solaris2*): Document the step-by-step procedure to bootstrap and...

	* doc/install.texi (*-*-solaris2*): Document the step-by-step
	procedure to bootstrap and install.
	Document the preference for the legacy Sun tools in /usr/bin
	over the POSIX tools in /usr/xpg4/bin for the build process.

Co-Authored-By: Phil Edwards <phil@jaj.com>
From-SVN: r69495

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index cbc6bc0eecd0e9f7cb668a5f60895289668dc8bd..7fcfdfc65912c7763763fa455d900c164288c92f 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,11 @@
+2003-07-17  Eric Botcazou <ebotcazou@libertysurf.fr>
+            Phil Edwards <phil@jaj.com>
+
+       * doc/install.texi (*-*-solaris2*): Document the step-by-step
+       procedure to bootstrap and install.
+       Document the preference for the legacy Sun tools in /usr/bin
+       over the POSIX tools in /usr/xpg4/bin for the build process.
+
 2003-07-17  Neil Booth  <neil@daikokuya.co.uk>
 
        * c.opt: Document Uncodumented; use it.  Document ObjC options.

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 3cad57de68ddd7b336ac48942228e6cfbb50eb52..5daa1351002df53ae79b7a3bb64d23e1bb0d3864 100644 (file)
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -3104,8 +3104,20 @@ GCC you first have to install a pre-built compiler, see our
 
 The Solaris 2 @command{/bin/sh} will often fail to configure
 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}.  We therefore
-recommend to set @env{CONFIG_SHELL} to @command{/bin/ksh} in your
-environment.
+recommend to use the following sequence of commands to bootstrap and
+install GCC:
+
+@smallexample
+   % CONFIG_SHELL=/bin/ksh
+   % export CONFIG_SHELL
+   % @var{srcdir}/configure [@var{options}] [@var{target}]
+   % gmake bootstrap
+   % gmake install
+@end smallexample
+
+As explained in the @uref{build.html,,build} instructions, we recommend
+to use GNU make, which we call @command{gmake} here to distinguish it
+from Sun make.
 
 Solaris 2 comes with a number of optional OS packages.  Some of these
 are needed to use GCC fully, namely @code{SUNWarc},
@@ -3124,6 +3136,10 @@ Trying to use the linker and other tools in
 For example, the linker may hang indefinitely.  The fix is to remove
 @file{/usr/ucb} from your @env{PATH}.
 
+The build process works more smoothly with the legacy Sun tools so, if you
+have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
+@file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
+
 All releases of GNU binutils prior to 2.11.2 have known bugs on this
 platform.  We recommend the use of GNU binutils 2.11.2 or the vendor
 tools (Sun @command{as}, Sun @command{ld}).