NetBSD/gnu/dist/toolchain
2002-09-25 20:05:14 +00:00
..
bfd Add missing parens that caused PLT slots >=32768 to jump to the wrong place. 2002-09-25 20:05:14 +00:00
binutils remove old and unused files 2002-06-24 06:49:14 +00:00
config
contrib
etc
gas wrong arg to memset. OpenBSD PR 2822 2002-07-16 23:08:04 +00:00
gcc -D__STRONGARM__ for -mcpu=strongarm* 2002-09-21 00:26:47 +00:00
gdb Make sure to write back correct FP state. Fixes port-i386/17927. 2002-09-17 07:05:09 +00:00
gprof 2002-08-16 Nick Clifton <nickc@redhat.com> 2002-08-17 03:03:53 +00:00
include Add some EF_VAX flags. (not yet used) 2002-03-28 06:52:57 +00:00
install
intl then -> than. 2002-01-07 14:54:09 +00:00
ld Add an armeb-*-netbsdelf* target (big-endian ARM). 2002-05-20 14:24:22 +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 Use <string.h> to get the memcpy/memset prototype. 2002-04-08 14:48:31 +00:00
libio Whack the atexit(_IO_cleanup), as per ../../libio/cleanup.c 1.2, for the same 2002-07-17 18:01:22 +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++ Tag all version strings with "nb1" to make FSF/binutils/gcc/gdb people 2001-12-19 21:32:49 +00:00
mmalloc
opcodes * vax-dis.c (print_insn_arg): Pass the insn info to print_insn_mode. 2002-04-28 05:27:46 +00:00
readline Fix a "comparison is always true" warning from gcc-current by passing 2002-05-06 18:25:46 +00:00
sim Correct obviously wrong memset() args. OK'd by itojun. 2002-07-20 16:51:43 +00:00
texinfo Tag all version strings with "nb1" to make FSF/binutils/gcc/gdb people 2001-12-19 21:32:49 +00:00
.brik
ChangeLog
config-ml.in
config.guess Add an armeb-*-netbsdelf* target (big-endian ARM). 2002-05-20 14:24:22 +00:00
config.if
config.sub Add an armeb-*-netbsdelf* target (big-endian ARM). 2002-05-20 14:24:22 +00:00
configure
configure.in Add an armeb-*-netbsdelf* target (big-endian ARM). 2002-05-20 14:24:22 +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.