NetBSD/gnu/dist/toolchain
2003-12-04 02:00:07 +00:00
..
config
contrib
etc
gcc Set USER_LABEL_PREFIX to "", otherwise native compilation of some GNU 2003-11-03 10:07:34 +00:00
include add the prototype for lbasename here where it belongs. 2003-03-01 15:31:34 +00:00
install
intl merge binutils 2.13.2.1 2003-03-01 12:25:55 +00:00
libchill
libf2c
libiberty merge binutils 2.13.2.1 2003-03-01 12:25:55 +00:00
libio Include <string.h>. From Ian Lance Taylor. 2003-05-06 02:31:06 +00:00
libobjc
libstdc++
texinfo Consistently comment out rules which attempt to rebuild .info from .texinfo, 2003-03-02 13:11:04 +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 If host is x86-*-netbsd*, don't descend into gcc, gdb, and rcs 2003-10-23 02:58:49 +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
makefile.vms
md5.sum
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.