freebsd-dev/contrib/gdb
John-Mark Gurney 85e5839202 recognize the FreeBSD ARCH tag that is put on binaries like on armeb
EABI binaries...

MFC after:	1 week
2014-02-12 02:03:37 +00:00
..
gdb recognize the FreeBSD ARCH tag that is put on binaries like on armeb 2014-02-12 02:03:37 +00:00
include Revive files which were pulled from the vendor branch only to be 2004-06-20 20:36:15 +00:00
config-ml.in Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
COPYING
COPYING.LIB
djunpack.bat Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
FREEBSD-diffs Implement functions necessary for compiling fbsd-threads.c. 2011-08-06 17:52:25 +00:00
FREEBSD-upgrade Update the upgrade instructions. 2004-06-25 05:04:09 +00:00
FREEBSD-Xlist - Use gdb-* glob instead of gdb-6.1.1, to simplify future imports. 2009-04-07 20:15:51 +00:00
gettext.m4 Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
install-sh Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
libtool.m4 Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
ltcf-c.sh Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
ltcf-cxx.sh Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
ltcf-gcj.sh Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
ltconfig Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
ltmain.sh Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
md5.sum Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
missing Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
mkinstalldirs Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
move-if-change Revive files which were pulled from the vendor branch only to be 2004-06-20 20:36:15 +00:00
README
src-release Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
symlink-tree Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +00:00
ylwrap Import of GDB version 6.1.1 (stripped; see FREEBSD-Xlist rev. 1.6). 2004-06-20 18:26:14 +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 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.