This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: automatic dependency tracking for gdbserver
- From: Tom Tromey <tromey at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 07 Dec 2012 07:43:34 -0700
- Subject: Re: RFC: automatic dependency tracking for gdbserver
- References: <87r4n6vnqx.fsf@fleche.redhat.com> <50C1C285.5070904@redhat.com>
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> I think I'd mildly prefer having these listed explicitly in
Pedro> acinclude.m4, so you can do just autoreconf on the command line
Pedro> or aclocal, without worrying about forgetting -I (IIRC,
Pedro> ACLOCAL_AMFLAGS is actually ignored, because we're not using
Pedro> automake). WDYT?
Sure, I will make that change.
Pedro> I actually have a patch for GDB that does the
Pedro> same to gdb's aclocal.
I think the change would be fine, but gdb does actually use this
variable:
$(srcdir)/aclocal.m4: @MAINTAINER_MODE_TRUE@ $(aclocal_m4_deps)
cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
gdbserver doesn't seem to have these maintainer-mode rebuild rules.
All these little details are a benefit of automake; but I looked at that
a bit and it is kind of a pain to switch over.
Pedro> I do wonder why does acinclude.m4 use sinclude instead of
Pedro> include. I don't see why you'd ever want those includes to
Pedro> silently fail.
Yeah, that is weird.
Tom