NetBSD/gnu/dist/toolchain
2001-03-20 00:03:27 +00:00
..
bfd Rather than hacking it with __NetBSD__, leverage ld --traditional-format to 2001-02-09 17:23:46 +00:00
binutils Show "-d" in the usage output for strip(1). 2001-01-30 19:24:54 +00:00
config Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
contrib
etc Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
gas Add cast to last change to ensure value fits in destination ((char) added). 2001-02-02 19:00:18 +00:00
gcc pull across a few changes from gcc-current for sparc64: 2001-03-06 05:21:47 +00:00
gdb Remove some debug printfs. 2001-02-05 19:39:45 +00:00
gprof Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
include Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
install
INSTALL
intl
ld Resolve conflicts from binutils 2.10.1 import. 2001-01-30 19:08:57 +00:00
libchill
libf2c
libiberty exit() -> _exit() when coupled with our [true] vfork(). 2001-01-30 19:45:09 +00:00
libio
libobjc Merge from gnu/dist: 2001-01-31 15:22:51 +00:00
libstdc++
mmalloc
opcodes
readline don't allow others to read the history file [from OpenBSD] 2001-03-20 00:03:27 +00:00
sim
texinfo Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
.brik
ChangeLog
config-ml.in Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
config.guess Fix frobbing of UNAME_RELEASE (meant to strip _{ALPHA,BETA} endings); it 2001-02-02 16:49:11 +00:00
config.if
config.sub Resolve conflicts from binutils 2.10.1 import. 2001-01-30 19:08:57 +00:00
configure Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
configure.in Add cases for m68k4k-*-netbsd* and vax1k-*-netbsd*. 2001-02-02 16:56:29 +00:00
COPYING
COPYING.LIB
FAQ
faq.html
install-sh
ltconfig Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
ltmain.sh Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
MAINTAINERS
Makefile.in Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
makefile.vms Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
missing Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
mkdep Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
mkinstalldirs
move-if-change
mpw-build.in Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
mpw-config.in Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
mpw-configure Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
mpw-install Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
mpw-README Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
README Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
setup.com Import binutils 2.10.1. 2001-01-30 18:32:08 +00:00
symlink-tree
ylwrap

		   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.