From: Mike Frysinger <vapier@gentoo.org>
To: binutils@sourceware.org
Subject: [PATCH 2/3] bfd: rename core.texi to corefile.texi
Date: Mon, 20 Dec 2021 02:16:24 -0500 [thread overview]
Message-ID: <20211220071625.29229-2-vapier@gentoo.org> (raw)
In-Reply-To: <20211220071625.29229-1-vapier@gentoo.org>
This is a generated file name from a correspondingly named C file.
Rename it to avoid unique build rules since there's no difference
to the generated manual.
---
bfd/.gitignore | 2 +-
bfd/doc/Makefile.am | 5 +----
bfd/doc/Makefile.in | 5 +----
bfd/doc/bfd.texi | 2 +-
4 files changed, 4 insertions(+), 10 deletions(-)
diff --git a/bfd/.gitignore b/bfd/.gitignore
index d4f7423111e5..065ed99f3a89 100644
--- a/bfd/.gitignore
+++ b/bfd/.gitignore
@@ -24,7 +24,7 @@
/doc/cache.texi
/doc/chew
/doc/coffcode.texi
-/doc/core.texi
+/doc/corefile.texi
/doc/elf.texi
/doc/elfcode.texi
/doc/format.texi
diff --git a/bfd/doc/Makefile.am b/bfd/doc/Makefile.am
index 787eb27db92d..473e9e6fc71f 100644
--- a/bfd/doc/Makefile.am
+++ b/bfd/doc/Makefile.am
@@ -21,7 +21,7 @@ AUTOMAKE_OPTIONS = info-in-builddir no-texinfo.tex foreign
DOCFILES = aoutx.texi archive.texi archures.texi \
bfdt.texi cache.texi coffcode.texi \
- core.texi elf.texi elfcode.texi format.texi \
+ corefile.texi elf.texi elfcode.texi format.texi \
libbfd.texi bfdwin.texi bfdio.texi \
opncls.texi reloc.texi section.texi \
syms.texi targets.texi init.texi hash.texi linker.texi \
@@ -110,9 +110,6 @@ bfd.stamp: ; @touch $@
bfdt.stamp: $(srcdir)/../bfd.c $(srcdir)/doc.str $(MKDOC)
$(AM_V_GEN)$(REGEN_TEXI)
-core.stamp: $(srcdir)/../corefile.c $(srcdir)/doc.str $(MKDOC)
- $(AM_V_GEN)$(REGEN_TEXI)
-
bfdver.texi: $(srcdir)/Makefile.in
@echo "creating $@"; \
echo "@set VERSION $(VERSION)" > bfdver.texi; \
diff --git a/bfd/doc/bfd.texi b/bfd/doc/bfd.texi
index 6f66dee7f304..4409b563095e 100644
--- a/bfd/doc/bfd.texi
+++ b/bfd/doc/bfd.texi
@@ -261,7 +261,7 @@ structures.
@include reloc.texi
@node Core Files, Targets, Relocations, BFD front end
-@include core.texi
+@include corefile.texi
@node Targets, Architectures, Core Files, BFD front end
@include targets.texi
--
2.33.0
next prev parent reply other threads:[~2021-12-20 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 7:16 [PATCH 1/3] bfd: replace doc header generation with pattern rules Mike Frysinger
2021-12-20 7:16 ` Mike Frysinger [this message]
2022-01-22 14:38 ` [PATCH 2/3] bfd: rename core.texi to corefile.texi Nick Clifton
2021-12-20 7:16 ` [PATCH 3/3] bfd: merge doc subdir up a level Mike Frysinger
2022-01-22 14:39 ` Nick Clifton
2022-01-23 15:05 ` H.J. Lu
2022-01-23 19:38 ` Mike Frysinger
2022-01-22 14:37 ` [PATCH 1/3] bfd: replace doc header generation with pattern rules Nick Clifton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211220071625.29229-2-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).