Go to file
Andrew Burgess 9ed5be5650 gdbsupport: regenerate Makefile.in
I had cause to regenerate gdbsupport/Makefile.in, and noticed some
unexpected changes in the copyright header dates.

I suspect that this was caused by the end of year date range update
process.

The Makefile.in contains two date ranges.  The first range appears to
be the date range for the version of automake being used, that is the
range runs up to 2017 only, when automake 1.15.1 was released.

The second date range in Makefile.in represents the date range for the
generated file, and so, now runs up to 2022.

Anyway, this is the result of running autoreconf (using automake
1.15.1) in the gdbsupport directory.
2022-01-11 10:10:51 +00:00
bfd Automatic date update in version.in 2022-01-11 00:00:20 +00:00
binutils Revert previous delta to debug.c. Replace with patch to reject indirect types that point to indirect types. 2022-01-07 12:34:37 +00:00
config unify 64-bit bfd checks 2022-01-01 12:49:07 -05:00
contrib
cpu
elfcpp Update year range in copyright notice of binutils files 2022-01-02 12:04:28 +10:30
etc Update year range in copyright notice of binutils files 2022-01-02 12:04:28 +10:30
gas XCOFF: add support for TLS relocations on hidden symbols 2022-01-10 09:14:57 +01:00
gdb gdb: add Tiezhu Yang to MAINTAINERS 2022-01-10 14:36:36 +08:00
gdbserver Do not use CC_HAS_LONG_LONG 2022-01-07 14:00:33 -07:00
gdbsupport gdbsupport: regenerate Makefile.in 2022-01-11 10:10:51 +00:00
gnulib
gold infinite recursion detected in gold testcase 2022-01-05 16:55:57 +10:30
gprof Update year range in copyright notice of binutils files 2022-01-02 12:04:28 +10:30
include elf: Set p_align to the minimum page size if possible 2022-01-05 05:06:18 -08:00
intl
ld XCOFF: add support for TLS relocations on hidden symbols 2022-01-10 09:14:57 +01:00
libbacktrace
libctf Update year range in copyright notice of binutils files 2022-01-02 12:04:28 +10:30
libdecnumber
libiberty Update year range in copyright notice of binutils files 2022-01-02 12:04:28 +10:30
opcodes aarch64: Add support for new SME instructions 2022-01-06 16:22:54 +00:00
readline
sim sim: ppc: migrate to standard uintXX_t types 2022-01-06 01:17:39 -05:00
texinfo
zlib
.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.