From: llandwerlin at gmail.com <llandwerlin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/8] autoconf: added AUTOHEADER variable
Date: Fri, 30 Apr 2010 02:24:11 +0200 [thread overview]
Message-ID: <1272587053-19535-7-git-send-email-llandwerlin@gmail.com> (raw)
In-Reply-To: <1272587053-19535-1-git-send-email-llandwerlin@gmail.com>
From: Lionel Landwerlin <llandwerlin@gmail.com>
autoheader is used by autoreconf, therefor we need to give the right
path to this tools for host/target autoreconfiguration.
Signed-off-by: Lionel Landwerlin <llandwerlin@gmail.com>
---
package/autoconf/autoconf.mk | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/package/autoconf/autoconf.mk b/package/autoconf/autoconf.mk
index d82c2c5..b7c1fe4 100644
--- a/package/autoconf/autoconf.mk
+++ b/package/autoconf/autoconf.mk
@@ -17,7 +17,7 @@ AUTOCONF_CONF_ENV = EMACS="no" ac_cv_path_M4=$(HOST_DIR)/usr/bin/m4 \
AUTOCONF_DEPENDENCIES = microperl host-m4
HOST_AUTOCONF_CONF_ENV = ac_cv_path_M4=$(HOST_DIR)/usr/bin/m4 \
- ac_cv_prog_gnu_m4_gnu=no
+ ac_cv_prog_gnu_m4_gnu=no
HOST_AUTOCONF_DEPENDENCIES = host-m4 host-libtool
@@ -26,4 +26,5 @@ $(eval $(call AUTOTARGETS,package,autoconf,host))
# variables used by other packages
AUTOCONF:=$(HOST_DIR)/usr/bin/autoconf
-AUTORECONF=$(HOST_CONFIGURE_OPTS) ACLOCAL="$(ACLOCAL)" $(HOST_DIR)/usr/bin/autoreconf -v -f -i -I "$(ACLOCAL_DIR)"
+AUTOHEADER:=$(HOST_DIR)/usr/bin/autoheader
+AUTORECONF=$(HOST_CONFIGURE_OPTS) ACLOCAL="$(ACLOCAL)" AUTOHEADER="$(AUTOHEADER)" $(HOST_DIR)/usr/bin/autoreconf -v -f -i -I "$(ACLOCAL_DIR)"
--
1.7.0.4
next prev parent reply other threads:[~2010-04-30 0:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 0:24 [Buildroot] [pull request] Fixes for 2010.05 llandwerlin at gmail.com
2010-04-30 0:24 ` [Buildroot] [PATCH 1/8] package: Force copy of .la files at the post install hook (readonly files might be problematic) llandwerlin at gmail.com
2010-05-02 7:32 ` Peter Korsgaard
2010-04-30 0:24 ` [Buildroot] [PATCH 2/8] package: Add $(HOST_DIR)/usr/lib to LD_LIBRARY_PATH for host but not target llandwerlin at gmail.com
2010-05-01 12:10 ` [Buildroot] [PATCH] " llandwerlin at gmail.com
2010-04-30 0:24 ` [Buildroot] [PATCH 3/8] scripts: force copy of files to erase already present and readonly files llandwerlin at gmail.com
2010-05-02 7:33 ` Peter Korsgaard
2010-04-30 0:24 ` [Buildroot] [PATCH 4/8] package: added PKG_CONF_ENV variables to host packages llandwerlin at gmail.com
2010-05-01 11:08 ` Thomas Petazzoni
2010-05-02 7:31 ` Peter Korsgaard
2010-04-30 0:24 ` [Buildroot] [PATCH 5/8] libtool: added LIBTOOLIZE variable to point on $(HOST_DIR)/usr/bin/libtoolize llandwerlin at gmail.com
2010-05-01 11:08 ` Thomas Petazzoni
2010-05-02 7:34 ` Peter Korsgaard
2010-04-30 0:24 ` llandwerlin at gmail.com [this message]
2010-05-01 11:08 ` [Buildroot] [PATCH 6/8] autoconf: added AUTOHEADER variable Thomas Petazzoni
2010-05-02 7:38 ` Peter Korsgaard
2010-04-30 0:24 ` [Buildroot] [PATCH 7/8] autoconf: added missing AUTOMAKE variable setting llandwerlin at gmail.com
2010-05-01 11:09 ` Thomas Petazzoni
2010-05-02 7:41 ` Peter Korsgaard
2010-04-30 0:24 ` [Buildroot] [PATCH 8/8] autoconf: added AUTOCONF " llandwerlin at gmail.com
2010-05-01 11:09 ` Thomas Petazzoni
2010-05-02 7:42 ` Peter Korsgaard
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=1272587053-19535-7-git-send-email-llandwerlin@gmail.com \
--to=llandwerlin@gmail.com \
--cc=buildroot@busybox.net \
/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