X-Git-Url: http://git.sourceforge.jp/view?p=pf3gnuchains%2Fgcc-fork.git;a=blobdiff_plain;f=README;h=3a495133bee688ccd2e6c8e3b9d614d5a3cc3e6f;hp=eb0e436d860f1d7412643b7ea4525ecaf4a773bc;hb=7db325f3b1ce568c13381d6da66485636e2a59f8;hpb=28e9041cc224267271fbcd8db22bea115912365b

diff --git a/README b/README
index eb0e436d860..3a495133bee 100644
--- a/README
+++ b/README
@@ -1,47 +1,17 @@
-		   README for GNU development tools
+This directory contains the GNU Compiler Collection (GCC).
 
-This directory contains various GNU compilers, assemblers, linkers, 
-debuggers, etc., plus their support routines, definitions, and documentation.
+The GNU Compiler Collection is free software.  See the file COPYING
+for copying permission.  The manuals, and some of the runtime
+libraries, are under different terms; see the individual source files
+for details.
 
-If you are receiving this as part of a GDB release, see the file gdb/README.
-If with a binutils release, see binutils/README;  if with a libg++ release,
-see libg++/README, etc.  That'll give you info about this
-package -- supported targets, how to use it, how to report bugs, etc.
+The directory INSTALL contains copies of the installation information
+as HTML and plain text.  The source of this information is
+gcc/doc/install.texi.  The installation information includes details
+of what is included in the GCC sources and what files GCC installs.
 
-It is now possible to automatically configure and build a variety of
-tools with one command.  To build all of the tools contained herein,
-run the ``configure'' script here, e.g.:
+See the file gcc/doc/gcc.texi (together with other files that it
+includes) for usage and porting information.  An online readable
+version of the manual is in the files gcc/doc/gcc.info*.
 
-	./configure 
-	make
-
-To install them (by default in /usr/local/bin, /usr/local/lib, etc),
-then do:
-	make install
-
-(If the configure script can't determine your type of computer, give it
-the name as an argument, for instance ``./configure sun4''.  You can
-use the script ``config.sub'' to test whether a name is recognized; if
-it is, config.sub translates it to a triplet specifying CPU, vendor,
-and OS.)
-
-If you have more than one compiler on your system, it is often best to
-explicitly set CC in the environment before running configure, and to
-also set CC when running make.  For example (assuming sh/bash/ksh):
-
-	CC=gcc ./configure
-	make
-
-A similar example using csh:
-
-	setenv CC gcc
-	./configure
-	make
-
-Much of the code and documentation enclosed is copyright by
-the Free Software Foundation, Inc.  See the file COPYING or
-COPYING.LIB in the various directories, for a description of the
-GNU General Public License terms under which you can copy the files.
-
-REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
-on where and how to report problems.
+See http://gcc.gnu.org/bugs.html for how to report bugs usefully.