Hi, autoconfers
I've gotten a report from a user with having locale-related problems
running the configure script that I supply. In other words, it works
fine when running with LC_ALL=C but not in some other locales. What's
failing is:
expr "x$ac_package" : ".*[^-a-zA-Z0-9_]" >/dev/null &&
{ echo "configure: error: invalid package name: $ac_package" >&2; exit 1; }
Dunno why that would fail in some non-C locale, but the safest thing
seems to be to always run in a predictable locale and configure does
that but further down from the argument parsing. I've tried the
following simple patch and it seems to work with simple tests.
Comments?
/assar
2000-10-17 Assar Westerlund <[EMAIL PROTECTED]>
* acgeneral.m4: move _AC_INIT_PREPARE_ENVIRONMENT earlier so that
we keep the same known environment for more of the script
Index: acgeneral.m4
===================================================================
RCS file: /cvs/autoconf/acgeneral.m4,v
retrieving revision 1.573
diff -u -w -u -w -r1.573 acgeneral.m4
--- acgeneral.m4 2000/10/16 18:40:19 1.573
+++ acgeneral.m4 2000/10/16 22:53:39
@@ -1274,6 +1274,7 @@
# Values which defaults can be set from `configure.in'.
define([_AC_INIT_DEFAULTS],
[AC_DIVERT_PUSH([DEFAULTS])dnl
+_AC_INIT_PREPARE_ENVIRONMENT
#
# Initializations.
@@ -2006,7 +2007,6 @@
# 5. Required macros (cache, default AC_SUBST etc.)
define([_AC_INIT_PREPARE],
[AC_DIVERT_PUSH([INIT_PREPARE])dnl
-_AC_INIT_PREPARE_ENVIRONMENT
trap 'rm -fr conftest* confdefs* core core.* *.core $ac_clean_files; exit 1' 1 2 15
