Go to file
2001-03-01 01:39:22 +00:00
bfd 2001-02-28 Andreas Jaeger <aj@suse.de> 2001-02-28 12:32:10 +00:00
binutils Remove non-K&R compliant LHS type cast in call to GET_DATA_ALLOC macro. 2001-02-28 19:40:12 +00:00
config Add s390 support 2001-02-10 00:58:38 +00:00
etc
gas 2001-02-28 Andreas Jaeger <aj@suse.de>, Bo Thorsen <bo@suse.de> 2001-02-28 12:49:40 +00:00
gdb Create new file regcache.h. Update all uses. 2001-03-01 01:39:22 +00:00
gprof Bump version to 2.11.90, fix missing dependencies in bfd/, 2001-02-27 06:43:56 +00:00
include new defines for Coldfire V4. 2001-02-28 23:47:10 +00:00
intl
ld Bump version to 2.11.90, fix missing dependencies in bfd/, 2001-02-27 06:43:56 +00:00
libiberty merge from gcc 2001-02-17 00:11:29 +00:00
mmalloc
opcodes new defines for Coldfire V4. 2001-02-28 23:47:10 +00:00
readline * rltty.c (save_tty_chars): Fix compilation-stopping typo. 2001-01-08 14:57:30 +00:00
sim Add support for disabling alignment checks when performing GDB interface 2001-02-28 01:04:24 +00:00
texinfo
.cvsignore
ChangeLog 2001-02-22 Jeff Johnston <jjohnstn@redhat.com> 2001-02-22 22:26:34 +00:00
config-ml.in
config.guess Add s390 support 2001-02-10 00:58:38 +00:00
config.if
config.sub Add s390 support 2001-02-10 00:58:38 +00:00
configure * configure: Output host type to stdout, not stderr. 2001-02-07 01:06:43 +00:00
configure.in Allow configuration of texinfo for Cygwin hosts. 2001-02-17 00:53:44 +00:00
COPYING
COPYING.LIB
COPYING.NEWLIB 2001-02-22 Jeff Johnston <jjohnstn@redhat.com> 2001-02-22 22:26:34 +00:00
djunpack.bat
gettext.m4
install-sh
libtool.m4 * ltcf-gcj.sh (lt_simple_link_test_code): Remove stray `(0)'. 2001-01-24 02:27:02 +00:00
ltcf-c.sh * ltcf-c.sh (ld_shlibs) [aix5*]: Disable on unknown CPU types. 2001-01-27 19:22:59 +00:00
ltcf-cxx.sh * ltcf-cxx.sh (ac_cv_prog_cc_pic_works, ac_cv_prog_cc_static_works): 2001-01-27 19:36:45 +00:00
ltcf-gcj.sh * ltcf-c.sh (ld_shlibs) [aix5*]: Disable on unknown CPU types. 2001-01-27 19:22:59 +00:00
ltconfig * ltconfig: Shell portability fix for the tagname validity check. 2001-01-27 19:34:13 +00:00
ltmain.sh * ltmain.sh (TAG disable-shared, TAG disable-static): Make sure we 2001-01-24 20:09:37 +00:00
MAINTAINERS General cleanup. 2001-01-16 05:30:31 +00:00
Makefile.in 2001-01-20 Maciej W. Rozycki <macro@ds2.pg.gda.pl> 2001-01-20 16:57:28 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
README-maintainer-mode
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.