Binutils with MCST patches
Go to file
Simon Marchi 89725b0d53 gdbsupport: re-generate Makefile.in
It looks like after doing last minute changes to Makefile.am in commit
06b3c5bdb ("gdbsupport: rename source files to .cc"), I forgot to
re-generate Makefile.in.  This patch fixes it.

gdbsupport/ChangeLog:

	* Makefile.in: Re-generate.
2020-03-03 17:11:12 -05:00
bfd bfd_check_format_matches preserving matches vs. cleanups 2020-03-03 21:45:01 +10:30
binutils Remove a call to abort which can be triggered by running objdump on a corrupt input file. 2020-03-03 16:11:12 +00:00
config Merge changes from GCC for the config/ directory 2020-02-19 17:51:24 +00:00
contrib
cpu
elfcpp
etc
gas x86: Replace IgnoreSize/DefaultSize with MnemonicSize 2020-03-03 11:24:26 -08:00
gdb gdb/fortran: Fix printing of logical true values for Flang 2020-03-03 18:20:18 +00:00
gdbserver gdbserver: Add mechanism to prevent sending T stop packets 2020-03-02 15:06:35 +00:00
gdbsupport gdbsupport: re-generate Makefile.in 2020-03-03 17:11:12 -05:00
gnulib gdb: update gnulib import 2020-02-22 20:37:18 -05:00
gold Updated translations for some of the binutils sub-directories. 2020-02-24 14:52:34 +00:00
gprof Updated translations for some of the binutils sub-directories. 2020-02-24 14:52:34 +00:00
include Add missing AT tags to the ELF common header. 2020-03-03 13:13:53 +00:00
intl Regen with blessed automake-1.15.1 2020-02-20 13:02:24 +10:30
ld Note that the --rpath-link command line option will search the contents of the SEARCH_DIR linker script directive, if one is provided. 2020-03-03 12:53:00 +00:00
libctf
libdecnumber
libiberty Import latest fixes to libiberty from GCC 2020-03-02 03:56:36 -08:00
opcodes x86: Replace IgnoreSize/DefaultSize with MnemonicSize 2020-03-03 11:24:26 -08:00
readline
sim
texinfo
zlib Merge changes from GCC for the config/ directory 2020-02-19 17:51:24 +00:00
.cvsignore
.gitattributes
.gitignore
ar-lib
ChangeLog
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
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
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
multilib.am
README
README-maintainer-mode
setup.com
src-release.sh
symlink-tree
test-driver
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.