changeset 1289:a7c9fd67ff7a

If the cross compiler supports internationalization, bash tries to stick -lintl into the host compiler, which may not support it. And if you stick a "no" for the question into config.cache it retests. So stick in a "nyet", which isn't a yes (so -lintl isn't added) but doesn't trigger a retest. I hate autoconf.
author Rob Landley <rob@landley.net>
date Sun, 21 Nov 2010 14:02:05 -0600
parents c054a7a36cd9
children cb39dec15ad2
files sources/sections/bash.build
diffstat 1 files changed, 1 insertions(+), 1 deletions(-) [+]
line wrap: on
line diff
--- a/sources/sections/bash.build	Wed Nov 17 22:09:19 2010 -0600
+++ b/sources/sections/bash.build	Sun Nov 21 14:02:05 2010 -0600
@@ -1,5 +1,5 @@
 # wire around some tests ./configure can't run when cross-compiling.
-echo -e "ac_cv_func_setvbuf_reversed=no\nbash_cv_sys_named_pipes=yes\nbash_cv_have_mbstate_t=yes\nbash_cv_getenv_redef=no" > config.cache &&
+echo -e "ac_cv_func_setvbuf_reversed=no\nbash_cv_sys_named_pipes=yes\nbash_cv_have_mbstate_t=yes\nbash_cv_getenv_redef=no\nac_cv_func_bindtextdomain=nyet" > config.cache &&
 LDFLAGS="$STATIC_FLAGS $LDFLAGS" CC="${ARCH}-cc" RANLIB="${ARCH}-ranlib" \
   ./configure --prefix="$STAGE_DIR" \
   --build="${CROSS_HOST}" --host="${CROSS_TARGET}" --cache-file=config.cache \