NetBSD/gnu/dist
bouyer 1352a07d69 Patch from Jason Thorpe: add a --write option, equivalent to the
"set write" command, for ease of use and compatibility with old gdb.
1997-10-30 10:39:53 +00:00
..
bfd Fixes to make new gdb compile on vax. 1997-10-20 12:44:24 +00:00
binutils stock binutils-2.8.1 1997-09-24 18:54:18 +00:00
config
etc
gas stock binutils-2.8.1 1997-09-24 18:54:18 +00:00
gdb Patch from Jason Thorpe: add a --write option, equivalent to the 1997-10-30 10:39:53 +00:00
gprof stock binutils-2.8.1 1997-09-24 18:54:18 +00:00
include stock binutils-2.8.1 1997-09-24 18:54:18 +00:00
ld stock binutils-2.8.1 1997-09-24 18:54:18 +00:00
libiberty Pull in <string.h> to get prototypes so that this builds on the Alpha. 1997-10-25 01:57:10 +00:00
opcodes stock binutils-2.8.1 1997-09-24 18:54:18 +00:00
readline Include string.h for prototypes so this builds on the Alpha. 1997-10-25 02:02:02 +00:00
texinfo stock binutils-2.8.1 1997-09-24 18:54:18 +00:00
COPYING
COPYING.LIB
Makefile.in stock binutils-2.8.1 1997-09-24 18:54:18 +00:00
README
config-ml.in
config.guess
config.sub
configure
configure.bat
configure.in
install.sh
makeall.bat
makefile.vms
move-if-change
mpw-README
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
setup.com
symlink-tree

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