NetBSD/gnu/dist/toolchain
thorpej 06811a827d Go back to the nop/unop pattern, and pick up rev. 1.35 from the
master FSF sources (rth):

	* config/tc-alpha.c (alpha_handle_align): Encode unop with RB as $sp.
2001-12-18 00:33:35 +00:00
..
bfd Add support for building sh-*-netbsdelf (elf32-sh-big) and 2001-12-15 02:18:24 +00:00
binutils add missing o: to the strip(1) getopt format string. 2001-08-20 04:47:29 +00:00
config
contrib
etc
gas Go back to the nop/unop pattern, and pick up rev. 1.35 from the 2001-12-18 00:33:35 +00:00
gcc Apply rev 1.4 of gnu/dist/gcc/config/sh/sh.h: 2001-12-16 18:56:45 +00:00
gdb Make this compile. Still needs work. 2001-12-16 07:26:22 +00:00
gprof Need <stdlib.h> for getenv() protoype (to avoid warning on LP64). 2001-10-05 18:48:01 +00:00
include Resolve conflicts from binutils 2.11.2 import 2001-08-14 04:43:05 +00:00
install
INSTALL
intl
ld After discussing the entry point issue w/ rth@redhat.com, add an 2001-12-16 04:06:51 +00:00
libchill
libf2c These two files make .PATH:ing a PITA, because they have the same names as 2001-07-18 20:42:58 +00:00
libiberty Add a missing va_end. 2001-09-24 14:33:50 +00:00
libio include <unistd.h> on NetBSD to get vfork() prototype (rename) 2001-07-26 17:18:39 +00:00
libobjc Provide an extern decl for strlen() all the time, not just if __alpha__ 2001-10-05 07:38:22 +00:00
libstdc++ Merge change from src/gnu/dist/libstdc++ [tv]: 2001-05-30 10:51:55 +00:00
mmalloc
opcodes From the master FSF sources, rev. 1.7 (rth): 2001-12-18 00:31:52 +00:00
readline Do not compare to chars to >= 0 since this will cause a warning where 2001-08-30 02:15:42 +00:00
sim Don't use $< in non-implicit rules. Instead, name the source explicitly. 2001-11-15 15:21:53 +00:00
texinfo Import binutils 2.11.2. 2001-08-14 02:57:43 +00:00
.brik
ChangeLog
config-ml.in
config.guess
config.if
config.sub New toolchain files for mipseb. Mainly toolchain2netbsd output with some 2001-11-08 07:21:53 +00:00
configure
configure.in Add support for building sh-*-netbsdelf (elf32-sh-big) and 2001-12-15 02:18:24 +00:00
COPYING
COPYING.LIB
FAQ
faq.html
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.in Import binutils 2.11.2. 2001-08-14 02:47:42 +00:00
makefile.vms
md5.sum Import binutils 2.11.2. 2001-08-14 02:47:42 +00:00
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
setup.com
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.