From 0c7dcad0e171fe6d3be4377dfa69dafbf290165d Mon Sep 17 00:00:00 2001
From: ebotcazou <ebotcazou@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Mon, 10 Apr 2006 14:29:47 +0000
Subject: [PATCH] * doc/install.texi (*-*-solaris2*): Point to the
configuration page.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@112823 138bc75d-0d04-0410-961f-82ee72b054a4
---
gcc/ChangeLog | 4 ++++
gcc/doc/install.texi | 5 ++---
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 248e539fcdb6..2e2bd9ee8788 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2006-04-10 Eric Botcazou <ebotcazou@libertysurf.fr>
+
+ * doc/install.texi (*-*-solaris2*): Point to the configuration page.
+
2006-04-10 Jakub Jelinek <jakub@redhat.com>
PR debug/27057
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index ec9f7ad32f1a..f859f56d22b8 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -3664,15 +3664,14 @@ GCC you first have to install a pre-built compiler, see the
The Solaris 2 @command{/bin/sh} will often fail to configure
@file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
-recommend to use the following sequence of commands to bootstrap and
-install GCC:
+recommend using the following initial sequence of commands
@smallexample
% CONFIG_SHELL=/bin/ksh
% export CONFIG_SHELL
@end smallexample
-and then proceed as described in @uref{build.html,,the build instructions}.
+and proceed as described in @uref{configure.html,,the configure instructions}.
In addition we strongly recommend specifying an absolute path to invoke
@var{srcdir}/configure.
--
GitLab