git
/
gcc
mirror of git://gcc.gnu.org/git/gcc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

README: Remove installation instructions and refer to the INSTALL directory instead. 

* README: Remove installation instructions and refer to the
	INSTALL directory instead.

From-SVN: r22747
This commit is contained in:
Gerald Pfeifer 1998-10-02 11:22:08 +02:00 committed by Gerald Pfeifer
parent e430f7389f
commit f2d11dcdd0
2 changed files with 7 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
Tue Sep 1 16:23:11 1998 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* README: Remove installation instructions and refer to the
INSTALL directory instead.
Wed Sep 30 22:20:50 1998 Robert Lipe <robertl@dgii.com> Wed Sep 30 22:20:50 1998 Robert Lipe <robertl@dgii.com>
* config.sub: Add support for i[34567]86-pc-udk. * config.sub: Add support for i[34567]86-pc-udk.

34
README
View File

@ -3,40 +3,10 @@
This directory contains various GNU compilers, assemblers, linkers, This directory contains various GNU compilers, assemblers, linkers,
debuggers, etc., plus their support routines, definitions, and documentation. debuggers, etc., plus their support routines, definitions, and documentation.
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.
It is now possible to automatically configure and build a variety of Check the INSTALL directory for detailed configuration and installation
tools with one command. To build all of the tools contained herein, instructions.
run the ``configure'' script here, e.g.:
./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 Much of the code and documentation enclosed is copyright by
the Free Software Foundation, Inc. See the file COPYING or the Free Software Foundation, Inc. See the file COPYING or