Binutils with MCST patches
Go to file
Tom Tromey cda75e7050 Rearrange Python breakpoint node in documentation
I noticed that the Python breakpoint documentation was ordered a bit
oddly.  It documented the constructor; then the stop method; then the
watchpoint constants (used for the constructor); then various other
methods and attributes; then the other constants used by the
constructor; and then finally some more methods and attributes.

This patch rearranges the node a little to move the constants to just
after the constructor and before the other methods and attributes.

2016-07-13  Tom Tromey  <tom@tromey.com>

	* python.texi (Breakpoints In Python): Move table of types and
	table of watchpoint types earlier in node.
2016-07-13 13:20:58 -06:00
bfd Automatic date update in version.in 2016-07-13 00:00:19 +00:00
binutils PR20337, Objdump makes poor choice of symbols 2016-07-09 16:53:33 +09:30
config
cpu
elfcpp Add support for MIPS .rld_map section. 2016-06-20 12:16:26 -07:00
etc Fix compile time warning messages building with gcc v6.1.1 2016-06-13 10:49:26 +01:00
gas MIPS/opcodes: Address issues with NAL disassembly 2016-07-13 17:42:43 +01:00
gdb Rearrange Python breakpoint node in documentation 2016-07-13 13:20:58 -06:00
gold Fix gold testsuite failure with GCC 6. 2016-06-29 23:24:35 -07:00
gprof
include Fixes done to TLS. 2016-07-11 15:24:35 +02:00
intl
ld [ARC] Update test. 2016-07-11 15:41:23 +02:00
libdecnumber
libiberty Don't needlessly clear xmemdup allocated memory. 2016-05-31 20:34:47 +09:30
opcodes MIPS/opcodes: Address issues with NAL disassembly 2016-07-13 17:42:43 +01:00
readline
sim Add support for simulating big-endian AArch64 binaries. 2016-06-30 09:10:41 +01:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ChangeLog [TILEPro] Don't build gdb 2016-06-28 14:16:15 -04:00
compile
config-ml.in
config.guess Fix typo introduced during the most recent synchronization update. 2016-05-27 14:34:06 +01:00
config.rpath
config.sub
configure [TILEPro] Don't build gdb 2016-06-28 14:16:15 -04:00
configure.ac [TILEPro] Don't build gdb 2016-06-28 14:16:15 -04:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def
Makefile.in Add dependencies to configure rule 2016-05-28 22:36:04 +09:30
Makefile.tpl Add dependencies to configure rule 2016-05-28 22:36:04 +09:30
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release.sh
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.