Go to file
1998-12-07 15:54:34 +00:00
bfd Use signed values for signed relocaitons. 1998-12-07 13:23:17 +00:00
binutils * objdump.c (SFILE): Add size field. 1998-12-07 01:07:02 +00:00
config
gas Imrpve handling of erroneous input. 1998-12-07 15:54:34 +00:00
gdb 1998-12-03 Jason Molenda (jsm@bugshack.cygnus.com) 1998-12-04 04:46:18 +00:00
gprof * gprof.texi (Symspecs): Mention that you have to add any 1998-12-07 02:58:45 +00:00
include * i386.h (i386_optab): Permit w suffix on processor control and 1998-12-06 18:22:55 +00:00
intl
ld * configure.tgt (m68*-*-gnu*): New target. From Aymeric Vincent 1998-12-06 21:34:37 +00:00
mmalloc
opcodes * mips-opc.c (mips_builtin_opcodes): Add dmfc2 and dmtc2. 1998-12-07 00:01:16 +00:00
readline
sim * gxtool silence tweak 1998-12-05 11:46:32 +00:00
.cvsignore
.Sanitize For top level: 1998-11-25 01:10:52 +00:00
Build-A-Release.mk
ChangeLog
config-ml.in
config.guess
config.if
config.sub
configure
configure.bat
configure.in
COPYING
COPYING.LIB
DOC.Sanitize
install-sh
install-texi.in
Install.in
intro.texi
ltconfig
ltmain.sh
makeall.bat
Makefile.in
makefile.vms
mdate-sh
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
Pack-A-Progressive
README
setup.com
symlink-tree
tape-labels-tex.in
test-build.mk
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.