freebsd-dev/contrib/gdb
Gary Jennejohn 8a9a74a887 FreeBSD specific modifications.
Obtained from /usr/ports/devel/gdb.

2.2. candidate ?

Should I put $FreeBSD$ into these files ?
1997-01-15 21:49:58 +00:00
..
bfd Import GDB in its full glory (all 25mb). We'll put it on a diet once it's 1996-11-03 17:03:03 +00:00
gdb FreeBSD specific modifications. 1997-01-15 21:49:58 +00:00
include Import GDB in its full glory (all 25mb). We'll put it on a diet once it's 1996-11-03 17:03:03 +00:00
libiberty Import GDB in its full glory (all 25mb). We'll put it on a diet once it's 1996-11-03 17:03:03 +00:00
opcodes Import GDB in its full glory (all 25mb). We'll put it on a diet once it's 1996-11-03 17:03:03 +00:00
readline/doc Import GDB in its full glory (all 25mb). We'll put it on a diet once it's 1996-11-03 17:03:03 +00:00
COPYING Import GDB in its full glory (all 25mb). We'll put it on a diet once it's 1996-11-03 17:03:03 +00:00
COPYING.LIB Import GDB in its full glory (all 25mb). We'll put it on a diet once it's 1996-11-03 17:03:03 +00:00
Makefile.in Import GDB in its full glory (all 25mb). We'll put it on a diet once it's 1996-11-03 17:03:03 +00:00
README Import GDB in its full glory (all 25mb). We'll put it on a diet once it's 1996-11-03 17:03:03 +00:00

		   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 gas release, see gas/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 CC=gcc

A similar example using csh:

	setenv CC gcc
	./configure
	make CC=gcc

See etc/cfg-paper.texi, etc/configure.texi, and/or the README files in
various subdirectories, for more details.

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, gas/README, etc., for info on where and
how to report problems.