No description
Find a file
Jason Molenda 33f2d56778 [gdb/ChangeLog]
2004-09-10  Jason Molenda  (jmolenda@apple.com)

        * cli/cli-script.c (read_next_line): Accept zero or more whitespace
        chars after 'if' or 'while' commands in user-defined commands.

[gdb/testsuite/ChangeLog]
2004-09-10  Jason Molenda  (jmolenda@apple.com)

        * gdb.base/define.exp: Two new tests to verify zero space chars
        after 'if' and 'while' commands in a user-defined command is correctly
        parsed.

Approved here:
http://sources.redhat.com/ml/gdb-patches/2004-09/msg00160.html
http://sources.redhat.com/ml/gdb-patches/2004-09/msg00157.html
2004-09-10 23:12:12 +00:00
bfd * section.c (bfd_sections_find_if): Fix parameter name in 2004-09-10 21:16:27 +00:00
binutils PR 363 2004-09-09 11:52:41 +00:00
config 2004-08-31 Robert Bowdidge <bowdidge@apple.com> 2004-09-10 17:49:29 +00:00
contrib
cpu cpu/ 2004-08-27 09:32:02 +00:00
etc
gas * dw2gencfi.c (select_cie_for_fde): When separating CIE out 2004-09-09 13:32:46 +00:00
gdb [gdb/ChangeLog] 2004-09-10 23:12:12 +00:00
gprof
include opcodes/ 2004-09-09 12:42:37 +00:00
intl
ld Fix typo last entry 2004-09-08 23:44:28 +00:00
libiberty merge from gcc 2004-09-08 22:01:25 +00:00
mmalloc
opcodes opcodes/ 2004-09-09 12:42:37 +00:00
readline
sim * allinsn.exp: Add new tests. 2004-09-08 09:20:29 +00:00
texinfo
.cvsignore
ChangeLog 2004-09-09 Daniel Berlin <dberlin@dberlin.org> 2004-09-10 02:19:35 +00:00
config-ml.in
config.guess Import latest version from master repository. 2004-09-04 07:53:54 +00:00
config.if
config.sub Import latest version from master repository. 2004-09-04 07:53:54 +00:00
configure 2004-09-09 Daniel Berlin <dberlin@dberlin.org> 2004-09-10 02:19:35 +00:00
configure.in 2004-09-09 Daniel Berlin <dberlin@dberlin.org> 2004-09-10 02:19:35 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.def 2004-09-09 Daniel Berlin <dberlin@dberlin.org> 2004-09-10 02:19:35 +00:00
Makefile.in 2004-09-09 Daniel Berlin <dberlin@dberlin.org> 2004-09-10 02:19:35 +00:00
Makefile.tpl 2004-09-09 Daniel Berlin <dberlin@dberlin.org> 2004-09-10 02:19:35 +00:00
makefile.vms
missing 2004-09-07 Paolo Bonzini <bonzini@gnu.org> 2004-09-07 08:34:06 +00:00
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release * Makefile.def, configure.in, src-release: Remove useless, bogus 2004-08-12 22:59:53 +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.