From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: toolchain-devel@blackfin.uclinux.org
Subject: [PATCH] sim: use AC_REQUIRE with AC_PROG_CC
Date: Mon, 11 Jul 2011 23:32:00 -0000 [thread overview]
Message-ID: <1310418640-32168-1-git-send-email-vapier@gentoo.org> (raw)
The autoconf guys point out that our usage of AC_PROG_CC in the
SIM_AC_COMMON does not jive with their intended use.
http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
So utilize AC_REQUIRE to make the warnings go away and generate
the correct code with different autoconf versions.
Signed-off-by: Mike Frysinger <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.
---
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
next reply other threads:[~2011-07-11 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 23:32 Mike Frysinger [this message]
2011-10-17 17:01 ` Joel Brobecker
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=1310418640-32168-1-git-send-email-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=toolchain-devel@blackfin.uclinux.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