Skip to content

Commit

Permalink
* README: Remove installation instructions and refer to the
Browse files Browse the repository at this point in the history
	INSTALL directory instead.


git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@22747 138bc75d-0d04-0410-961f-82ee72b054a4
  • Loading branch information
gerald committed Oct 2, 1998
1 parent d73f157 commit de7dcc8
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 32 deletions.
5 changes: 5 additions & 0 deletions ChangeLog
Original file line number Diff line number Diff line change
@@ -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>

* config.sub: Add support for i[34567]86-pc-udk.
Expand Down
34 changes: 2 additions & 32 deletions README
Original file line number Diff line number Diff line change
Expand Up @@ -3,40 +3,10 @@
This directory contains various GNU compilers, assemblers, linkers,
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
tools with one command. To build all of the tools contained herein,
run the ``configure'' script here, e.g.:
Check the INSTALL directory for detailed configuration and installation
instructions.

./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
Expand Down

0 comments on commit de7dcc8

Please sign in to comment.