Name Last Update
..
CVS Loading commit data...
bfd Loading commit data...
config Loading commit data...
etc Loading commit data...
gdb Loading commit data...
include Loading commit data...
intl Loading commit data...
libiberty Loading commit data...
mmalloc Loading commit data...
opcodes Loading commit data...
readline Loading commit data...
sim Loading commit data...
texinfo Loading commit data...
utils Loading commit data...
COPYING Loading commit data...
COPYING.LIB Loading commit data...
GNUmakefile Loading commit data...
Makefile.def Loading commit data...
Makefile.in Loading commit data...
Makefile.tpl Loading commit data...
README Loading commit data...
config-ml.in Loading commit data...
config.guess Loading commit data...
config.if Loading commit data...
config.sub Loading commit data...
configure Loading commit data...
configure.in Loading commit data...
djunpack.bat Loading commit data...
gettext.m4 Loading commit data...
install-sh Loading commit data...
libtool.m4 Loading commit data...
ltcf-c.sh Loading commit data...
ltcf-cxx.sh Loading commit data...
ltcf-gcj.sh Loading commit data...
ltconfig Loading commit data...
ltmain.sh Loading commit data...
md5.sum Loading commit data...
missing Loading commit data...
mkinstalldirs Loading commit data...
move-if-change Loading commit data...
mpw-README Loading commit data...
mpw-build.in Loading commit data...
mpw-config.in Loading commit data...
mpw-configure Loading commit data...
mpw-install Loading commit data...
src-release Loading commit data...
symlink-tree Loading commit data...
ylwrap Loading commit data...
		   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.