From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: automatic dependency tracking for gdbserver
Date: Fri, 07 Dec 2012 14:43:00 -0000 [thread overview]
Message-ID: <87pq2lx6qx.fsf@fleche.redhat.com> (raw)
In-Reply-To: <50C1C285.5070904@redhat.com> (Pedro Alves's message of "Fri, 07 Dec 2012 10:18:45 +0000")
>>>>> "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
next prev parent reply other threads:[~2012-12-07 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 21:18 Tom Tromey
2012-12-07 3:12 ` Joel Brobecker
2012-12-07 10:18 ` Pedro Alves
2012-12-07 14:43 ` Tom Tromey [this message]
2013-01-16 19:48 ` Make autoreconf under gdb/ work (Re: RFC: automatic dependency tracking for gdbserver) Pedro Alves
2013-01-16 21:15 ` Tom Tromey
2013-01-17 11:08 ` Pedro Alves
2012-12-10 20:15 ` RFC: automatic dependency tracking for gdbserver Tom Tromey
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=87pq2lx6qx.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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