public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: binutils@sourceware.org
Subject: [PATCH] opcodes: Remove i386-init.h and i386-tbl.h from HFILES
Date: Wed, 30 Nov 2022 13:48:02 -0800	[thread overview]
Message-ID: <20221130214802.32340-1-hjl.tools@gmail.com> (raw)

i386-init.h and i386-tbl.h are generated files.  There is nothing to
translate.  Remove them from HFILES (POTFILES).

	* Makefile.am (HFILES): Remove i386-init.h and i386-tbl.h.
	* Makefile.in: Regenerated.
	* po/POTFILES.in: Likewise.
---
 opcodes/Makefile.am    | 2 --
 opcodes/Makefile.in    | 2 --
 opcodes/po/POTFILES.in | 2 --
 3 files changed, 6 deletions(-)

diff --git a/opcodes/Makefile.am b/opcodes/Makefile.am
index 93e9002be19..cb6ff0ebc5e 100644
--- a/opcodes/Makefile.am
+++ b/opcodes/Makefile.am
@@ -64,9 +64,7 @@ HFILES = \
 	epiphany-desc.h epiphany-opc.h \
 	fr30-desc.h fr30-opc.h \
 	frv-desc.h frv-opc.h \
-	i386-init.h \
 	i386-opc.h \
-	i386-tbl.h \
 	ia64-asmtab.h \
 	ia64-opc.h \
 	ip2k-desc.h ip2k-opc.h \
diff --git a/opcodes/Makefile.in b/opcodes/Makefile.in
index fe4539d6097..5524af5ccd2 100644
--- a/opcodes/Makefile.in
+++ b/opcodes/Makefile.in
@@ -455,9 +455,7 @@ HFILES = \
 	epiphany-desc.h epiphany-opc.h \
 	fr30-desc.h fr30-opc.h \
 	frv-desc.h frv-opc.h \
-	i386-init.h \
 	i386-opc.h \
-	i386-tbl.h \
 	ia64-asmtab.h \
 	ia64-opc.h \
 	ip2k-desc.h ip2k-opc.h \
diff --git a/opcodes/po/POTFILES.in b/opcodes/po/POTFILES.in
index 24f57af24a3..9906bf14848 100644
--- a/opcodes/po/POTFILES.in
+++ b/opcodes/po/POTFILES.in
@@ -73,10 +73,8 @@ h8300-dis.c
 hppa-dis.c
 i386-dis.c
 i386-gen.c
-i386-init.h
 i386-opc.c
 i386-opc.h
-i386-tbl.h
 ia64-asmtab.c
 ia64-asmtab.h
 ia64-dis.c
-- 
2.38.1


                 reply	other threads:[~2022-11-30 21:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221130214802.32340-1-hjl.tools@gmail.com \
    --to=hjl.tools@gmail.com \
    --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).