From: Joel Brobecker <brobecker@adacore.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org, toolchain-devel@blackfin.uclinux.org
Subject: Re: [PATCH] sim: use AC_REQUIRE with AC_PROG_CC
Date: Mon, 17 Oct 2011 17:01:00 -0000 [thread overview]
Message-ID: <20111017165724.GC17942@adacore.com> (raw)
In-Reply-To: <1310418640-32168-1-git-send-email-vapier@gentoo.org>
> 2011-07-11 Mike Frysinger <vapier@gentoo.org>
>
> * aclocal.m4 (SIM_AC_COMMON): Call AC_REQUIRE on AC_PROG_CC.
> Delete direct call to AC_PROG_CC.
Looks, OK, except why did you move the call up?
Looking at the autoconf documentation, AC_CONFIG_HEADER does not need
to be called right after AC_INIT, it is only customary. So if there is
a reason for us to change the location of the use of AC_PROG_CC, we
probably want to fix the comment as well.
> ---
> sim/common/aclocal.m4 | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/sim/common/aclocal.m4 b/sim/common/aclocal.m4
> index 264cced..3ed5efd 100644
> --- a/sim/common/aclocal.m4
> +++ b/sim/common/aclocal.m4
> @@ -24,11 +24,11 @@ sinclude([../../config/zlib.m4])
>
> AC_DEFUN([SIM_AC_COMMON],
> [
> +AC_REQUIRE([AC_PROG_CC])
> # autoconf.info says this should be called right after AC_INIT.
> AC_CONFIG_HEADER(ifelse([$1],,config.h,[$1]):config.in)
> AC_CANONICAL_SYSTEM
> AC_ARG_PROGRAM
> -AC_PROG_CC
> AC_PROG_INSTALL
>
> # Put a plausible default for CC_FOR_BUILD in Makefile.
> --
> 1.7.6
--
Joel
next prev parent reply other threads:[~2011-10-17 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 23:32 Mike Frysinger
2011-10-17 17:01 ` Joel Brobecker [this message]
2011-10-17 17:17 ` Mike Frysinger
2011-10-17 18:23 ` Joel Brobecker
[not found] <1310418640-32168-1-git-send-email-vapier__8759.03008641235$1310418652$gmane$org@gentoo.org>
2011-07-12 19:48 ` 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=20111017165724.GC17942@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=toolchain-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.org \
/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