Hardcode m4 config instead of letting configure detect it automatically.
This hopefully fixes the build issues some (Ubuntu) users seems to be
having lately (E.G. #679).
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Additional fixes and cleanups.
- Updated/fixed packages: alsamixergui, coreutils, fltk, microperl,
- ncurses, vim
+ Updated/fixed packages: alsamixergui, autoconf, coreutils, fltk,
+ microperl, ncurses, vim
Issues resolved (http://bugs.uclibc.org):
AUTOCONF_INSTALL_TARGET_OPT = DESTDIR=$(TARGET_DIR) install
endif
-AUTOCONF_CONF_ENV = EMACS="no"
+AUTOCONF_CONF_ENV = EMACS="no" ac_cv_path_M4=$(HOST_DIR)/usr/bin/m4 \
+ ac_cv_prog_gnu_m4_gnu=no
AUTOCONF_DEPENDENCIES = microperl
$(HOST_CONFIGURE_OPTS) \
CFLAGS="$(HOST_CFLAGS)" \
LDFLAGS="$(HOST_LDFLAGS)" \
+ ac_cv_path_M4=$(HOST_DIR)/usr/bin/m4 \
+ ac_cv_prog_gnu_m4_gnu=no \
./configure $(QUIET) \
--prefix="$(HOST_DIR)/usr" \
--sysconfdir="$(HOST_DIR)/etc" \