From: Jan Beulich <jbeulich@suse.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] x86: Remove libopcodes dependency
Date: Thu, 24 Nov 2022 11:19:05 +0100 [thread overview]
Message-ID: <6a5d4918-919a-8b6b-822b-17ce38488629@suse.com> (raw)
In-Reply-To: <20221122181927.251937-1-hjl.tools@gmail.com>
On 22.11.2022 19:19, H.J. Lu wrote:
> --- a/gas/Makefile.am
> +++ b/gas/Makefile.am
> @@ -446,6 +446,12 @@ development.exp: $(BFDDIR)/development.sh
> $(EGREP) "(development|experimental)=" $(BFDDIR)/development.sh \
> | $(AWK) -F= '{ print "set " $$1 " " $$2 }' > $@
>
> +$(srcdir)/../opcodes/i386-init.h $(srcdir)/../opcodes/i386-tbl.h: \
> + @MAINT@ $(srcdir)/../opcodes/i386-opc.tbl \
> + $(srcdir)/../opcodes/i386-reg.tbl \
> + $(srcdir)/../opcodes/i386-opc.h
> + cd ../opcodes; make gen-i386-tbl
I've made a patch to gas/Makefile.am as you have requested in reply to
my series. I will want to put that through some more testing, so I will
submit a v3 of that only a little later (and of course only unless you
submit a v2 of your patch earlier that I would also end up being okay
with). In the course of doing so I noticed a few more issues with your
change:
For one I don't think you can put @MAINT@ on a continued line, as the
line continuation might then be hidden when @MAINT@ expands to #. The
list of dependencies wants expressing via a variable, which would then
be used immediately after @MAINT@ without any line continuation
following.
And then your rule / dependency won't be enough on a "maintainer-clean"
tree, i.e. when the generated headers aren't there at all, and when
config/.deps/tc-i386.Po is still empty. In that case nothing would
trigger their generation; an explicit dependency of config/tc-i386.o on
these headers needs adding here.
Finally you're missing a dependency of the generated headers on
i386-gen.c.
Jan
next prev parent reply other threads:[~2022-11-24 10:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 18:19 H.J. Lu
2022-11-23 8:36 ` Jan Beulich
2022-11-28 23:43 ` H.J. Lu
2022-11-29 9:12 ` Jan Beulich
2022-11-24 10:19 ` Jan Beulich [this message]
2022-11-28 23:49 ` [PATCH v2] " H.J. Lu
2022-11-29 9:22 ` Jan Beulich
2022-11-29 19:38 ` H.J. Lu
2022-11-30 0:06 ` H.J. Lu
2022-11-30 6:58 ` Jan Beulich
2022-11-30 22:22 ` H.J. Lu
2022-12-01 7:41 ` Jan Beulich
2022-12-01 18:26 ` [PATCH v3] " H.J. Lu
2022-12-02 7:16 ` Jan Beulich
2022-12-02 17:19 ` H.J. Lu
2022-12-05 11:25 ` Jan Beulich
2022-11-30 7:31 ` [PATCH v2] " Jan Beulich
2022-11-30 22:15 ` H.J. Lu
2022-12-01 7:21 ` Jan Beulich
2022-12-01 18:20 ` H.J. Lu
2022-12-02 7:10 ` Jan Beulich
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=6a5d4918-919a-8b6b-822b-17ce38488629@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
/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).