From: Simon Horman <horms@verge.net.au>
To: "Aníbal Limón" <anibal.limon@linux.intel.com>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] configure.ac: Fix failure caused by x32 ABI test
Date: Thu, 9 Apr 2015 11:10:13 +0900 [thread overview]
Message-ID: <20150409021013.GA32707@verge.net.au> (raw)
In-Reply-To: <1428515338-4374-1-git-send-email-anibal.limon@linux.intel.com>
On Wed, Apr 08, 2015 at 12:48:58PM -0500, Aníbal Limón wrote:
> When try to compile with zlib fails due to configure.ac
> bad expansion caused by x32 ABI test that needs AC_PROG_CC
> for use AC_EGREP_CPP.
>
> Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Thanks for following up on this, applied.
> ---
> configure.ac | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index 1ecadd5..e0b5f78 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -8,6 +8,7 @@ AC_INIT(kexec-tools, 2.0.10.git)
> AC_CONFIG_AUX_DIR(./config)
> AC_CONFIG_HEADERS([include/config.h])
> AC_LANG(C)
> +AC_PROG_CC
>
> AC_DEFINE_UNQUOTED(PACKAGE_DATE, "`date '+%d %B %Y'`",
> [Define to the release date of this package])
> @@ -106,9 +107,6 @@ AC_ARG_WITH([booke],
>
> dnl ---Programs
> dnl To specify a different compiler, just 'export CC=/path/to/compiler'
> -
> -AC_PROG_CC
> -
> if test "${build}" != "${host}" ; then
> AC_CHECK_PROGS(BUILD_CC, [${build_alias}-gcc ${build}-gcc gcc])
> else
> --
> 1.9.1
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2015-04-09 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 17:48 [PATCH] configure.ac: Fix failure caused by x32 ABI test Aníbal Limón
2015-04-09 2:10 ` Simon Horman [this message]
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=20150409021013.GA32707@verge.net.au \
--to=horms@verge.net.au \
--cc=anibal.limon@linux.intel.com \
--cc=kexec@lists.infradead.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