NetBSD/gnu/dist
matt d7585142e2 Include VAX instruction disassembly support into bfd. (XXX case[lbw] still
needs to be done.)
1998-10-29 17:31:10 +00:00
..
bfd TARGET_PAGE_SIZE should be 4k. 1998-10-18 08:48:59 +00:00
binutils Add -t (totals) option as requested by <mrg@eterna.com.au> in PR bin/6133. 1998-09-14 18:01:46 +00:00
config
etc
gas In non-BFD assemblers on NetBSD, use the NetBSD method of indicating 1998-10-25 00:26:36 +00:00
gcc More PIC fixes. 1998-10-28 15:56:20 +00:00
gdb
gprof
include Include VAX instruction disassembly support into bfd. (XXX case[lbw] still 1998-10-29 17:31:10 +00:00
ld
libf2c Import egcs 1.1 (branch), 14 Oct 1998 sources 1998-10-14 14:35:59 +00:00
libiberty Nuke stdio.h's P_tmpdir and explicitly try /tmp after the environment 1998-09-14 17:19:35 +00:00
libio Import egcs 1.1 (branch), 14 Oct 1998 sources 1998-10-14 14:35:59 +00:00
libstdc++
opcodes Include VAX instruction disassembly support into bfd. (XXX case[lbw] still 1998-10-29 17:31:10 +00:00
readline
sim
texinfo
COPYING
COPYING.LIB
Makefile.in
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.