From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: 'Tom Tromey' <tromey@redhat.com>,
'Andreas Schwab' <schwab@linux-m68k.org>,
gdb-patches@sourceware.org
Subject: Re: Patch: FYI: use AC_HELP_STRING
Date: Wed, 22 Apr 2009 18:02:00 -0000 [thread overview]
Message-ID: <20090422180151.GB22514@adacore.com> (raw)
In-Reply-To: <000901c9c318$a3bf3b60$eb3db220$@u-strasbg.fr>
> Why not, but currently only files with suffix ".l", ".y", ".h" and ".c"
> are listed in gdb_find.sh, and that list
> is currently used by gdb_ari.sh.
>
> Will AC_HELP_STRING appear in one of these files?
> Currently I see AC_HELP_STRING and AS_HELP_STRING
> only in gdb/configure.ac file,
> which means that gdb_ari.sh will not be useful.
AC_HELP_STRING is an autoconf macro, so it's not just configure.ac.
It could also be any of the .m4 files: aciclude.m4, aclocal.m4, etc.
I didn't realize that these files weren't already ARI'ed. If it's too
much trouble, then we don't have to add a rule for this. It looks like
it would be very easy to fix any regression when the macro disappears,
so reintroducing it wouldn't be really all that harmful.
So I'm fine either way: We can decide to start checking the autoconf
files or not.
--
Joel
next prev parent reply other threads:[~2009-04-22 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 16:59 Tom Tromey
2009-04-21 17:08 ` Andreas Schwab
2009-04-21 18:08 ` Tom Tromey
2009-04-21 21:01 ` Andreas Schwab
2009-04-21 21:07 ` Tom Tromey
2009-04-22 0:18 ` Tom Tromey
2009-04-22 0:59 ` Joel Brobecker
2009-04-22 1:45 ` Tom Tromey
2009-04-22 7:05 ` Pierre Muller
2009-04-22 18:02 ` Joel Brobecker [this message]
2009-04-22 21:45 ` Pierre Muller
2009-04-22 22:42 ` 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=20090422180151.GB22514@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=schwab@linux-m68k.org \
--cc=tromey@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