Binutils with MCST patches
Go to file
Jan Kratochvil ac46107c5c gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print'
After building GDB
	--with-python=/usr/bin/python3
and for example stripping ./gdb and running:
	./gdb -data-directory data-directory/ -iex "add-auto-load-safe-path $PWD/gdb-gdb.gdb" -iex "add-auto-load-safe-path $PWD/gdb-gdb.
py" ./gdb
I get:
	Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal]
	  File "/home/jkratoch/redhat/gdb-test-python3/gdb/gdb-gdb.py", line 91
	    print "Warning: Cannot find enum type_flag_value type."
								  ^
	SyntaxError: Missing parentheses in call to 'print'
	(top-gdb) q

gdb/ChangeLog
2016-02-22  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb-gdb.py (class TypeFlagsPrinter): Use parentheses for print.
2016-02-22 17:15:14 +01:00
bfd Remove BSF_COMMON from comments 2016-02-22 04:39:43 -08:00
binutils Add a missing break to readelf.c 2016-02-16 15:03:39 -08:00
config Sync top level files with gcc. 2016-02-10 10:54:29 +00:00
cpu epiphany/disassembler: Improve alignment of output. 2016-02-02 11:09:17 +00:00
elfcpp
etc
gas Add more const type qualifiers to GAS sources. 2016-02-22 14:11:27 +00:00
gdb gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print' 2016-02-22 17:15:14 +01:00
gold Pass -mrelax-relocations=yes to $(TEST_AS) 2016-02-16 06:00:03 -08:00
gprof
include [ARM] Add FP16 feature extension for ARMv8.2 architecture 2016-02-19 14:27:23 +00:00
intl
ld Skip pr19539 test for cris*-*-* targets 2016-02-20 14:45:25 -08:00
libdecnumber
libiberty
opcodes Add parentheses to prevent truncated addresses 2016-02-15 16:03:58 -08:00
readline
sim sim: mips: fix prog_bfd usage 2016-02-05 20:27:25 -05:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ChangeLog Sync top level files with gcc. 2016-02-10 10:54:29 +00:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure Sync top level files with gcc. 2016-02-10 10:54:29 +00:00
configure.ac Sync top level files with gcc. 2016-02-10 10:54:29 +00: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 Sync top level files with gcc. 2016-02-10 10:54:29 +00:00
Makefile.tpl Sync top level files with gcc. 2016-02-10 10:54:29 +00:00
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.