From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
Simon Marchi <simon.marchi@polymtl.ca>
Cc: GDB Patches <gdb-patches@sourceware.org>, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] Update gnulib/Makefile.in:aclocal_m4_deps
Date: Fri, 31 Aug 2018 11:21:00 -0000 [thread overview]
Message-ID: <a3aeaa0b-a38b-a699-8fbe-bdd29dac2a84@redhat.com> (raw)
In-Reply-To: <87bm9jiq05.fsf@redhat.com>
On 08/30/2018 09:00 PM, Sergio Durigan Junior wrote:
> On Thursday, August 30 2018, Simon Marchi wrote:
>
>> On 2018-08-30 11:57, Sergio Durigan Junior wrote:
>>> $(srcdir)/aclocal.m4: @MAINTAINER_MODE_TRUE@ $(aclocal_m4_deps)
>>> cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
>>
>> This looks good to me, the set of m4 files listed here matches the
>> list of actual m4 files in import/m4. Follow-up question, could we
>> use $(wildcard ...) instead of listing them by hand?
>
> Yeah, I think that could work. That's basically what I did to generate
> this list: "ls *.m4". If you want, I can edit the patch and make it use
> $(wildcard) before pushing it.
>
Really not sure that's a good idea. We don't use $wildcard for listing .c files
either, for example, and I think for good reason. It makes the set of files to build
dependent of what you happen to have or not have locally, instead of determined
statically. That in general affects development, changing git branches, etc.
Consider that GDB even links successfully if you miss including/linking some .c file
in the build, given the _initialize_foo registration mechanism. Maybe not so much
an issue with the m4 files, but I'd think a more principle approach to automate this
would be to make the update-gnulib.sh script generate/update a Makefile fragment
file that contained the aclocal_m4_deps m4 files list, check that file into the
tree, and then gdb/gnulib/Makefile.in would source/include that fragment file.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-08-31 11:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 19:59 [PATCH] Update gnulib to current upstream master Sergio Durigan Junior
2018-08-29 16:19 ` Tom Tromey
2018-08-29 16:29 ` Sergio Durigan Junior
2018-08-29 19:06 ` Pedro Alves
2018-08-29 19:34 ` Sergio Durigan Junior
2018-08-31 13:04 ` Pedro Alves
2018-08-30 0:04 ` Tom Tromey
2018-08-30 3:01 ` Sergio Durigan Junior
2018-08-30 15:57 ` [PATCH] Update gnulib/Makefile.in:aclocal_m4_deps Sergio Durigan Junior
2018-08-30 17:05 ` Simon Marchi
2018-08-30 20:00 ` Sergio Durigan Junior
2018-08-31 7:59 ` Joel Brobecker
2018-08-31 16:02 ` Sergio Durigan Junior
2018-08-31 11:21 ` Pedro Alves [this message]
2018-08-31 16:03 ` Sergio Durigan Junior
2018-09-02 21:21 ` [PATCH] Automatically update "aclocal_m4_deps" when updating gnulib Sergio Durigan Junior
2018-09-03 11:15 ` Pedro Alves
2018-09-03 21:18 ` Sergio Durigan Junior
2018-09-04 11:10 ` Pedro Alves
2018-09-04 17:58 ` Sergio Durigan Junior
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=a3aeaa0b-a38b-a699-8fbe-bdd29dac2a84@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.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