NetBSD/gnu/dist
thorpej 4a9e81df67 Pass in the appropriate machine directive to the assembler if an -mcpu=...
option is given to the compiler.  It's silly to have to specify it twice
on a command line (e.g. -mcpu=ev56 -Wa,-mev56), especially considering
that if you don't, and the compiler emits e.g. a BWX instruction, the
assembler will treat it as a macro, open-coding an equivalent, which can
have some serious unwanted side-effects in some situations.

Also, don't treat e.g. 21164 and ev5 as equivalent; the assembler treats
them differently: 21164 enables PALcode-only instructions, while ev5
does not.
1999-12-03 06:37:47 +00:00
..
bc s/ the the / the / 1999-10-08 20:13:42 +00:00
bfd Some time ago, bfd_target_vector was changed from beeing an array, to be 1999-10-04 18:47:33 +00:00
binutils Round 2 of gnu/dist cleanup: 1999-02-04 04:25:21 +00:00
config
diffutils Line up Info directory entries horizontally. 1999-02-12 13:01:24 +00:00
gas Add an m68k-*-netbsdelf* target. 1999-04-30 15:08:33 +00:00
gawk Back out the last change. 1999-08-17 19:35:11 +00:00
gcc Pass in the appropriate machine directive to the assembler if an -mcpu=... 1999-12-03 06:37:47 +00:00
gdb gdb for SH (doesn't work yet) 1999-11-26 09:13:36 +00:00
gprof Remove references to nonexistent manual pages prof(1), pc(1) and monitor(3). 1999-09-23 09:38:53 +00:00
grep -e may be specified multiple times, as per SUSv2. 1999-08-25 01:32:03 +00:00
include Round 2 of gnu/dist cleanup: 1999-02-04 04:25:21 +00:00
ld - set pagesize to 4K 1999-10-07 18:05:17 +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 Import libio changes from egcs 1.1.2. 1999-04-06 16:22:32 +00:00
libstdc++ Import libstdc++ changes from egcs 1.1.2. 1999-04-06 16:28:42 +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
COPYING
COPYING.LIB
Makefile.in
README
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.in
install.sh
ltconfig Add a blank "ltconfig" so that it is possible to generate config.h files 1999-02-03 17:08:23 +00:00
move-if-change
symlink-tree

README

		   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.