No description
Find a file
2004-08-05 23:35:14 +00:00
bfd daily update 2004-08-05 00:00:05 +00:00
binutils (deduce_name): Fix typos introduced when program_name was renamed to prog_name. 2004-08-02 08:14:17 +00:00
config ChangeLog: 2004-08-03 20:54:19 +00:00
contrib
cpu
etc
gas * write.c (relax_segment): Use was_address instead of address when 2004-08-05 16:55:00 +00:00
gdb * MAINTAINERS: Add self to Write-After-Approval. 2004-08-05 23:35:14 +00:00
gprof * gprof.c (main): For line-by-line profiling, there is no need to 2004-07-13 12:18:57 +00:00
include 2004-08-04 Andrew Cagney <cagney@gnu.org> 2004-08-04 23:44:32 +00:00
intl
ld * ld.texinfo (Top): Document specific options of 68HC11 and 68HC12. 2004-08-02 20:03:41 +00:00
libiberty merge from gcc 2004-06-29 12:51:56 +00:00
mmalloc
opcodes Added new instructions for next version of VIA PadLock core. 2004-07-30 12:36:38 +00:00
readline
sim * Makefile.in (GDB_INCLUDES): Remove bogus reference to mmalloc. 2004-08-05 21:14:06 +00:00
texinfo
.cvsignore
ChangeLog * configure.in (arm*-*-symbianelf*): Add ${libgcj} and 2004-08-04 16:12:06 +00:00
config-ml.in 2004-06-01 Paolo Bonzini <bonzini@gnu.org> 2004-06-01 07:46:01 +00:00
config.guess
config.if
config.sub Undo accidental commit whilst adding crx-elf port 2004-07-07 17:37:19 +00:00
configure * configure.in (arm*-*-symbianelf*): Add ${libgcj} and 2004-08-04 16:12:06 +00:00
configure.in * configure.in (arm*-*-symbianelf*): Add ${libgcj} and 2004-08-04 16:12:06 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
gettext.m4
install-sh
libtool.m4 knetbsd/kfreebsd patches from Robert Millan. 2004-07-21 19:21:41 +00:00
ltcf-c.sh knetbsd/kfreebsd patches from Robert Millan. 2004-07-21 19:21:41 +00:00
ltcf-cxx.sh knetbsd/kfreebsd patches from Robert Millan. 2004-07-21 19:21:41 +00:00
ltcf-gcj.sh knetbsd/kfreebsd patches from Robert Millan. 2004-07-21 19:21:41 +00:00
ltconfig knetbsd/kfreebsd patches from Robert Millan. 2004-07-21 19:21:41 +00:00
ltmain.sh
MAINTAINERS Include Makefile.*, not just Makefile.in, in the top-level policy. 2004-06-09 22:48:28 +00:00
Makefile.def 2004-08-03 Paolo Bonzini <bonzini@gnu.org> 2004-08-03 09:36:03 +00:00
Makefile.in 2004-08-03 Paolo Bonzini <bonzini@gnu.org> 2004-08-03 09:36:03 +00:00
Makefile.tpl 2004-08-03 Paolo Bonzini <bonzini@gnu.org> 2004-08-03 09:36:03 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release
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.