Go to file
Ulrich Weigand 91104499cb * gdbarch.sh (GET_LONGJMP_TARGET): Replace by gdbarch_get_longjmp_target.
* infrun.c (handle_inferior_event): Likewise.
	* gdbarch.sh (GET_LONGJMP_TARGET_P): Replace by
	gdbarch_get_longjmp_target_p.
	* breakpoint.c (breakpoint_re_set): Likewise.
	* infrun.c (handle_inferior_event): Likewise.
	* gdbarch.c, gdbarch.h: Regenerate.
2007-06-06 15:15:34 +00:00
bfd daily update 2007-06-06 00:00:08 +00:00
binutils PR binutils/4356 binutils/591 2007-06-06 08:02:47 +00:00
config 2007-06-04 Olivier Hainque <hainque@adacore.com> 2007-06-04 09:33:35 +00:00
cpu
elfcpp
etc
gas 2007-06-05 Paul Brook <paul@codesourcery.com> 2007-06-05 22:02:47 +00:00
gdb * gdbarch.sh (GET_LONGJMP_TARGET): Replace by gdbarch_get_longjmp_target. 2007-06-06 15:15:34 +00:00
gold Add support for SHF_MERGE sections. 2007-05-16 17:42:48 +00:00
gprof * regenerated files from updating libtool. 2007-05-24 18:12:51 +00:00
include include/ 2007-05-31 15:04:52 +00:00
intl
ld include/ 2007-05-31 15:04:52 +00:00
libiberty
opcodes 2007-06-05 Paul Brook <paul@codesourcery.com> 2007-06-05 22:02:47 +00:00
readline
sim * mips3264r2.igen (DSHD): Fix compile warning. 2007-05-15 12:20:32 +00:00
texinfo
.cvsignore
ChangeLog 2007-06-04 Paolo Bonzini <bonzini@gnu.org> 2007-06-04 08:32:52 +00:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure 2007-06-04 Paolo Bonzini <bonzini@gnu.org> 2007-06-04 08:32:52 +00:00
configure.ac 2007-06-04 Paolo Bonzini <bonzini@gnu.org> 2007-06-04 08:32:52 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4 2007-06-01 Steve Ellcey <sje@cup.hp.com> 2007-06-01 11:33:01 +00:00
ltgcc.m4 2007-05-31 Paolo Bonzini <bonzini@gnu.org> 2007-05-31 06:40:36 +00:00
ltmain.sh 2007-05-25 Andreas Tobler <a.tobler@schweiz.org> 2007-05-25 19:56:24 +00:00
ltoptions.m4 * ltmain.sh: Update from GCC. 2007-05-24 17:33:42 +00:00
ltsugar.m4 * ltmain.sh: Update from GCC. 2007-05-24 17:33:42 +00:00
ltversion.m4 * ltmain.sh: Update from GCC. 2007-05-24 17:33:42 +00:00
MAINTAINERS
Makefile.def 2007-05-16 Paolo Bonzini <bonzini@gnu.org> 2007-05-16 09:03:22 +00:00
Makefile.in 2007-05-16 Paolo Bonzini <bonzini@gnu.org> 2007-05-16 09:03:22 +00:00
Makefile.tpl 2007-05-16 Paolo Bonzini <bonzini@gnu.org> 2007-05-16 09:03:22 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release * ltmain.sh: Update from GCC. 2007-05-24 17:33:42 +00:00
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.