Go to file
David Ung 4b185e973e * mips16-opc.c (mips16_opcodes): Add the following MIPS16e
instructions to the table; seb/seh/sew/zeb/zeh/zew.
2005-06-16 17:01:12 +00:00
bfd * archive.c: Include "libiberty.h". 2005-06-16 08:05:39 +00:00
binutils rename.c (simple_copy): Only define if it is going to be used. 2005-06-16 09:18:19 +00:00
config PR libgcj/19877: 2005-06-14 20:27:38 +00:00
contrib
cpu 2005-06-15 Dave Brolley <brolley@redhat.com> 2005-06-15 15:33:07 +00:00
etc * bfd/Makefile.am, binutils/Makefile.am, etc/Makefile.in 2005-05-19 23:49:52 +00:00
gas gas: 2005-06-13 15:34:39 +00:00
gdb * MAINTAINERS (Write After Approval): Add self. 2005-06-16 15:04:39 +00:00
gprof Update the address of the FSF 2005-05-09 06:55:25 +00:00
include * hppa.h (pa_opcodes): Use cM and cX instead of cm and cx, 2005-06-11 15:33:52 +00:00
intl Update the address and telephone number of the FSF organization 2005-05-13 08:04:31 +00:00
ld Add quotes to avoid a null test expression. 2005-06-16 09:46:10 +00:00
libiberty merge from gcc 2005-05-28 19:49:24 +00:00
mmalloc
opcodes * mips16-opc.c (mips16_opcodes): Add the following MIPS16e 2005-06-16 17:01:12 +00:00
readline Fix typos in ChangeLog 2005-05-09 21:07:02 +00:00
sim * mips.igen: New mips16e model and include m16e.igen. 2005-06-16 15:15:49 +00:00
texinfo
.cvsignore
ChangeLog * depcomp: Update from automake CVS. Add 'ia64hp' stanza. 2005-06-13 18:01:01 +00:00
compile
config-ml.in
config.guess
config.sub * config.sub: Add cases for the Renesas m32c. (This patch has been 2005-06-02 21:23:04 +00:00
configure * configure.in <cris-*, crisv32-*>: Enable target-libffi again for 2005-06-07 09:33:44 +00:00
configure.in * configure.in <cris-*, crisv32-*>: Enable target-libffi again for 2005-06-07 09:33:44 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp * depcomp: Update from automake CVS. Add 'ia64hp' stanza. 2005-06-13 18:01:01 +00:00
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh PR libgcj/20160 2005-03-01 22:33:54 +00:00
MAINTAINERS
Makefile.def 2005-05-20 Paolo Bonzini <bonzini@gnu.org> 2005-05-20 07:16:11 +00:00
Makefile.in 2005-05-20 Paolo Bonzini <bonzini@gnu.org> 2005-05-20 07:16:11 +00:00
Makefile.tpl 2005-05-25 Paolo Bonzini <bonzini@gnu.org> 2005-05-25 14:23:03 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release
symlink-tree
ylwrap ./ 2005-05-15 18:19:45 +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

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.