No description
Find a file
Fernando Nasser 1302fd5e2b 2001-01-08 Fernando Nasser <fnasser@redhat.com>
* Makefile.in (install-gdbtk): Add .itcl files to the list of files
	to be installed.
2001-01-08 12:47:49 +00:00
bfd Update address for bug reports. 2001-01-07 14:53:57 +00:00
binutils Update address for bug reports. 2001-01-07 15:04:21 +00:00
config
etc
gas 2001-01-08 Bo Thorsen <bo@suse.de> 2001-01-08 09:37:43 +00:00
gdb 2001-01-08 Fernando Nasser <fnasser@redhat.com> 2001-01-08 12:47:49 +00:00
gprof Add GNU Free Documentation License 2000-11-06 20:27:26 +00:00
include * tc-i386.c (md_assemble): Handle third byte of the opcode as prefix. 2001-01-05 12:30:12 +00:00
intl
ld 2000-01-07 David O'Brien <obrien@BSDi.com> 2001-01-08 05:25:58 +00:00
libiberty * fnmatch.c: Make the note about the origins of this file more 2000-12-29 20:16:02 +00:00
mmalloc
opcodes * i386-dis.c: Add x86_64 support. 2001-01-05 11:11:54 +00:00
readline
sim 2001-01-06 Ben Elliston <bje@redhat.com> 2001-01-05 04:36:09 +00:00
texinfo
.cvsignore
ChangeLog * config.sub, config.guess: Update from subversions. 2001-01-07 12:04:21 +00:00
config-ml.in * config-ml.in (CC, CXX): Avoid trailing whitespace. 2000-08-22 05:01:20 +00:00
config.guess * config.sub, config.guess: Update from subversions. 2001-01-07 12:04:21 +00:00
config.if
config.sub * config.sub, config.guess: Update from subversions. 2001-01-07 12:04:21 +00:00
configure
configure.in * configure.in: Disable language-specific target libraries for 2000-12-12 20:33:05 +00:00
COPYING
COPYING.LIB
djunpack.bat
gettext.m4 * ltconfig, ltmain.sh: Updated from libtool multi-language branch. 2000-08-31 09:25:11 +00:00
install-sh
libtool.m4 * ltconfig, ltmain.sh, libtool.m4: Updated from libtool 2000-09-30 06:07:00 +00:00
ltcf-c.sh * ltconfig, ltmain.sh, libtool.m4, ltcf-c.sh: Updated from libtool 2000-09-06 13:27:41 +00:00
ltcf-cxx.sh * ltcf-cxx.sh: Added file, required by 2000-11-18 merge. 2000-11-20 17:27:59 +00:00
ltcf-gcj.sh ChangeLog 2000-11-23 04:04:00 +00:00
ltconfig * ltconfig, ltmain.sh, libtool.m4: Updated from libtool 2000-09-30 06:07:00 +00:00
ltmain.sh * ltconfig, ltmain.sh, libtool.m4: Updated from libtool 2000-09-30 06:07:00 +00:00
MAINTAINERS * add sid/ delegation 2000-12-07 21:29:37 +00:00
Makefile.in * Makefile.in: Merge with GCC and libgcj. 2000-11-18 22:01:34 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
README-maintainer-mode
setup.com
symlink-tree
ylwrap

		   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.