NetBSD/gnu/dist
christos a3b9ba9f0e In the NO_UNDERSCORES case we need an extra `*' in ASM_GENERATE_INTERNAL_LABEL
otherwise using the macro in dbxout.c, eats the initial `.'. Probably someone
forgot that one, because the `*' is present in other implementations.
... tv said go for it.
1999-01-07 10:22:49 +00:00
..
bfd NetBSD always saves a_midmag as big-endian, but libbfd use the same 1998-12-21 03:27:02 +00:00
binutils Add '-d' flag for compatibility with the old strip. 1998-12-22 23:04:41 +00:00
config
etc
gas Verify that the symbols are of the right kind when applying fixup 1999-01-02 19:25:40 +00:00
gcc In the NO_UNDERSCORES case we need an extra `*' in ASM_GENERATE_INTERNAL_LABEL 1999-01-07 10:22:49 +00:00
gdb Prevent gdb from getting stuck in _PROCEDURE_LINKAGE_TABLE_ () 1998-11-21 23:43:48 +00:00
gprof
include NetBSD specific things needed by the shared library support. 1998-11-21 22:38:40 +00:00
ld set ELFSIZE=32 here 1998-12-16 15:01:50 +00:00
libf2c Import egcs 1.1.1 (release). 1998-12-13 00:15:30 +00:00
libiberty Import egcs 1.1.1 (release). 1998-12-13 00:15:30 +00:00
libio Import egcs 1.1.1 (release). 1998-12-13 00:15:30 +00:00
libstdc++ Import egcs 1.1.1 (release). 1998-12-13 00:15:30 +00:00
opcodes Include VAX instruction disassembly support into bfd. (XXX case[lbw] still 1998-10-29 17:31:10 +00:00
readline
sim
texinfo
config-ml.in
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
configure
configure.bat
configure.in
COPYING
COPYING.LIB
install.sh
makeall.bat
Makefile.in
makefile.vms
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
setup.com
symlink-tree

		   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.