Go to file
Phil Blundell 63dc00f9ea Merge from mainline 2000-10-14 20:39:20 +00:00
config This commit was manufactured by cvs2svn to create branch 'binutils- 2000-04-04 14:32:33 +00:00
etc Add generated files. 2000-05-29 14:08:52 +00:00
include Merge from mainline 2000-10-14 20:39:20 +00:00
texinfo This commit was manufactured by cvs2svn to create branch 'binutils- 2000-04-04 14:32:33 +00:00
COPYING 19990502 sourceware import 1999-05-03 07:29:06 +00:00
COPYING.LIB 19990502 sourceware import 1999-05-03 07:29:06 +00:00
ChangeLog This commit was manufactured by cvs2svn to create branch 'binutils- 2000-04-04 14:32:33 +00:00
Makefile.in Add generated files. 2000-05-29 14:08:52 +00:00
README 19990502 sourceware import 1999-05-03 07:29:06 +00:00
config-ml.in 19990502 sourceware import 1999-05-03 07:29:06 +00:00
config.guess This commit was manufactured by cvs2svn to create branch 'binutils- 2000-04-04 14:32:33 +00:00
config.if 19990502 sourceware import 1999-05-03 07:29:06 +00:00
config.sub This commit was manufactured by cvs2svn to create branch 'binutils- 2000-04-04 14:32:33 +00:00
configure This commit was manufactured by cvs2svn to create branch 'binutils- 2000-04-04 14:32:33 +00:00
configure.in This commit was manufactured by cvs2svn to create branch 'binutils- 2000-04-04 14:32:33 +00:00
install-sh 19990502 sourceware import 1999-05-03 07:29:06 +00:00
ltconfig This commit was manufactured by cvs2svn to create branch 'binutils- 2000-04-04 14:32:33 +00:00
ltmain.sh This commit was manufactured by cvs2svn to create branch 'binutils- 2000-04-04 14:32:33 +00:00
makefile.vms 19990502 sourceware import 1999-05-03 07:29:06 +00:00
missing 19990502 sourceware import 1999-05-03 07:29:06 +00:00
mkdep This commit was manufactured by cvs2svn to create branch 'binutils- 2000-04-04 14:32:33 +00:00
mkinstalldirs 19990502 sourceware import 1999-05-03 07:29:06 +00:00
move-if-change 19990502 sourceware import 1999-05-03 07:29:06 +00:00
mpw-README 19990502 sourceware import 1999-05-03 07:29:06 +00:00
mpw-build.in 19990502 sourceware import 1999-05-03 07:29:06 +00:00
mpw-config.in 19990502 sourceware import 1999-05-03 07:29:06 +00:00
mpw-configure 19990502 sourceware import 1999-05-03 07:29:06 +00:00
mpw-install 19990502 sourceware import 1999-05-03 07:29:06 +00:00
setup.com 19990502 sourceware import 1999-05-03 07:29:06 +00:00
symlink-tree 19990502 sourceware import 1999-05-03 07:29:06 +00:00
ylwrap 19990502 sourceware import 1999-05-03 07:29:06 +00:00

README

		   README for GNU development tools

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.:

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