update the README for fixinc

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@38600 138bc75d-0d04-0410-961f-82ee72b054a4

1 files changed, 10 insertions, 11 deletions

diff --git a/gcc/fixinc/README b/gcc/fixinc/README
index 89c46ab522c..69e3b1fd718 100644
--- a/gcc/fixinc/README
+++ b/gcc/fixinc/README
@@ -2,26 +2,25 @@
 FIXINCLUDES OPERATION
 =====================
 
-See also:  http://autogen.linuxbox.com/fixincludes
+See also:  http://autogen.SourceForge.net/fixincludes
 
 The set of fixes required was distilled down to just the data required
 to specify what needed to happen for each fix.  Those data were edited
 into a file named gcc/fixinc/inclhack.def.  A program called
-AutoGen (http://autogen.linuxbox.com) uses these definitions to
-instantiate several different templates (gcc/fixinc/*.tpl) that then
+AutoGen (http://autogen.SourceForge.net, ver 4.x) uses these definitions
+to instantiate several different templates (gcc/fixinc/*.tpl) that then
 produces a fixincludes replacement shell script (inclhack.sh), a
-replacement binary program (fixincl.x) and a script to drive the
-binary fixincl.sh).
+replacement binary program (fixincl.x).
 
 If there is no special purpose script, then mkfixinc.sh will try to
-compile, link and test execute the binary version.  If it cannot be
-successfully built, the shell version will be used instead.  If
-mkfixinc.sh determines that your system needs machine-specific fixes
-that have not yet been applied to inclhack.def, it will install and
-use the current fixinc.* for that system instead.
+compile, link and execute the fixincl program.  Otherwise, it will
+install and use the current fixinc.* for that system instead.
+Also, on certain platforms (viz. those that do not have functional
+bidirectional pipes), the fixincl program is split into two.
+This should only concern you on DOS and BeOS.
 
 Regards,
-	Bruce <autogen@linuxbox.com>
+	Bruce <bkorb@gnu.org>