diff options
| author | Simon Marchi <simon.marchi@polymtl.ca> | 2019-09-18 09:07:44 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2019-09-18 09:09:15 -0400 |
| commit | e0b2a78c83207340f6c4b5dbe02bec850dbb7def (patch) | |
| tree | 512ef80bb7f04ee72f3c2a4b7fef0508161a5535 /opcodes/microblaze-dis.c | |
| parent | ed48ec2e6ec5514f01b9b3a810d6ddf39651114b (diff) | |
| download | gdb-e0b2a78c83207340f6c4b5dbe02bec850dbb7def.zip gdb-e0b2a78c83207340f6c4b5dbe02bec850dbb7def.tar.gz gdb-e0b2a78c83207340f6c4b5dbe02bec850dbb7def.tar.bz2 | |
Re-generate many configure and Makefile.in files
I get some spurious changes when running autoconf/automake for various
projects in the tree. This is likely because they were generated using
distro-patched tools last time.
I ran `autoreconf -f` in the various automake projects of the
binutils-gdb tree, and this is the result. The tools I am using have
been compiled from source, from the upstream release.
bfd/ChangeLog:
* Makefile.in: Re-generate.
* configure: Re-generate.
* doc/Makefile.in: Re-generate.
binutils/ChangeLog:
* Makefile.in: Re-generate.
* configure: Re-generate.
* doc/Makefile.in: Re-generate.
gas/ChangeLog:
* Makefile.in: Re-generate.
* configure: Re-generate.
* doc/Makefile.in: Re-generate.
gold/ChangeLog:
* testsuite/Makefile.in: Re-generate.
gprof/ChangeLog:
* Makefile.in: Re-generate.
* configure: Re-generate.
ld/ChangeLog:
* Makefile.in: Re-generate.
* configure: Re-generate.
opcodes/ChangeLog:
* Makefile.in: Re-generate.
* configure: Re-generate.
Diffstat (limited to 'opcodes/microblaze-dis.c')
0 files changed, 0 insertions, 0 deletions