NetBSD/gnu/dist
1999-04-06 16:20:26 +00:00
..
bc The .IP tag must be one word. 1999-03-09 02:52:05 +00:00
bfd Move the custom version of MACHTYPE_OK out where it belongs. 1999-04-03 05:26:06 +00:00
binutils Round 2 of gnu/dist cleanup: 1999-02-04 04:25:21 +00:00
config stock binutils-2.8 1997-09-24 15:39:15 +00:00
diffutils Line up Info directory entries horizontally. 1999-02-12 13:01:24 +00:00
gas Revert handling of divide and remainder assembler pseudo-ops (with 1999-03-31 18:01:31 +00:00
gcc Merge egcs 1.1.2 conflicts. 1999-04-06 16:04:00 +00:00
gdb Make gdb compile on sparc64. (Actually work correctly is another thing....) 1999-04-04 19:02:31 +00:00
gprof Line up Info directory entries horizontally. 1999-02-12 13:01:24 +00:00
grep Resolve conflicts from import. 1999-02-20 11:34:28 +00:00
include Round 2 of gnu/dist cleanup: 1999-02-04 04:25:21 +00:00
ld Implement "-nostdlib" and LD_NOSTD_PATH in binutils-based ld. 1999-02-05 19:48:07 +00:00
libf2c Import libf2c from egcs 1.1.2. 1999-04-06 16:20:26 +00:00
libiberty Round 2 of gnu/dist cleanup: 1999-02-04 04:25:21 +00:00
libio Do not pretend to be _POSIX_SOURCE if you aren't. 1999-02-24 01:40:52 +00:00
libstdc++ Round 2 of gnu/dist cleanup: 1999-02-04 04:25:21 +00:00
opcodes Round 2 of gnu/dist cleanup: 1999-02-04 04:25:21 +00:00
readline/doc Remove files not used by a native build. 1999-02-11 16:51:27 +00:00
sim Round 2 of gnu/dist cleanup: 1999-02-04 04:25:21 +00:00
texinfo Fix garbage message on getcwd(3) failure. 1999-02-19 04:15:20 +00:00
config-ml.in stock binutils-2.8 1997-09-24 15:39:15 +00:00
config.guess turn arm32 (uname -m) & NetBSD (uname -s) into arm-unknown-netbsdX.Y, so that it works for GNU naming 1998-12-16 14:19:54 +00:00
config.sub stock binutils-2.8 1997-09-24 15:39:15 +00:00
configure stock binutils-2.8 1997-09-24 15:39:15 +00:00
configure.in stock binutils-2.8 1997-09-24 15:39:15 +00:00
COPYING stock binutils-2.8 1997-09-24 15:39:15 +00:00
COPYING.LIB stock binutils-2.8 1997-09-24 15:39:15 +00:00
install.sh stock binutils-2.8 1997-09-24 15:39:15 +00:00
ltconfig Add a blank "ltconfig" so that it is possible to generate config.h files 1999-02-03 17:08:23 +00:00
Makefile.in stock binutils-2.8.1 1997-09-24 18:54:18 +00:00
move-if-change stock binutils-2.8 1997-09-24 15:39:15 +00:00
README stock binutils-2.8 1997-09-24 15:39:15 +00:00
symlink-tree stock binutils-2.8 1997-09-24 15:39:15 +00:00

		   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.