NetBSD/gnu/dist
2000-08-08 14:29:17 +00:00
..
bc
bfd Make sure the dynsym section and the reserved bits in the RPDR are fully 2000-06-11 23:47:56 +00:00
binutils
config
diffutils
gas
gawk
gcc fix two bugs: 2000-08-02 12:07:12 +00:00
gdb fix typo 2000-08-03 05:04:02 +00:00
gprof
grep
include
ld Pullover wording fix for "-e entry" from gnu/dist/toolchain. 2000-08-06 01:48:59 +00:00
libf2c
libiberty
libio
libstdc++
opcodes
postfix import patchlevel 8. bugfixes, plus adds the ability to filter on 2000-05-31 15:18:05 +00:00
readline/doc
sendmail sync with 8.11.0. (relatively large amount of changes are due to 2000-07-23 14:24:48 +00:00
sim
texinfo
toolchain redefine LINK_SPEC properly. 2000-08-08 14:29:17 +00:00
config-ml.in
config.guess
config.sub Add arm26 support to GCC. This is only very slightly tested at present. 2000-07-02 12:31:21 +00:00
configure
configure.in
COPYING
COPYING.LIB
install.sh
ltconfig
Makefile.in
move-if-change
README
README.toolchain A README file describing the `toolchain' directory import procedure, and 2000-07-26 00:40:02 +00:00
symlink-tree

		   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.