+2010-10-02 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
+
+ PR bootstrap/45326
+ PR bootstrap/45174
+ * configure.ac: Honor initial values of $build_configargs,
+ $host_configargs, $target_configargs. Mark the precious, so
+ environment settings get recorded.
+ * configure: Regenerate.
+
2010-10-02 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Sync from GCC:
CC_FOR_BUILD
AS_FOR_BUILD
AR_FOR_BUILD
-target_configargs
target_configdirs
configdirs
-host_configargs
build_configdirs
-build_configargs
INSTALL_GDB_TK
GDB_TK
CONFIGURE_GDB_TK
tooldir
GCC_SHLIB_SUBDIR
RPATH_ENVVAR
+target_configargs
+host_configargs
+build_configargs
BUILD_CONFIG
CXXFLAGS_FOR_TARGET
CFLAGS_FOR_TARGET
CXXFLAGS
CCC
CPP
+build_configargs
+host_configargs
+target_configargs
AR
AS
DLLTOOL
CXX C++ compiler command
CXXFLAGS C++ compiler flags
CPP C preprocessor
+ build_configargs
+ additional configure arguments for build directories
+ host_configargs
+ additional configure arguments for host directories
+ target_configargs
+ additional configure arguments for target directories
AR AR for the host
AS AS for the host
DLLTOOL DLLTOOL for the host
fi
baseargs="$baseargs --disable-option-checking"
+# Record and document user additions to sub configure arguments.
+
+
+
+
# For the build-side libraries, we just need to pretend we're native,
# and not use the same cache file. Multilibs are neither needed nor
# desired.
-build_configargs="--cache-file=../config.cache ${baseargs}"
+build_configargs="$build_configargs --cache-file=../config.cache ${baseargs}"
# For host modules, accept cache file option, or specification as blank.
case "${cache_file}" in
# Host dirs don't like to share a cache file either, horribly enough.
# This seems to be due to autoconf 2.5x stupidity.
-host_configargs="--cache-file=./config.cache ${extra_host_args} ${baseargs}"
+host_configargs="$host_configargs --cache-file=./config.cache ${extra_host_args} ${baseargs}"
-target_configargs=${baseargs}
+target_configargs="$target_configargs ${baseargs}"
# Passing a --with-cross-host argument lets the target libraries know
# whether they are being built with a cross-compiler or being built
fi
baseargs="$baseargs --disable-option-checking"
+# Record and document user additions to sub configure arguments.
+AC_ARG_VAR([build_configargs],
+ [additional configure arguments for build directories])
+AC_ARG_VAR([host_configargs],
+ [additional configure arguments for host directories])
+AC_ARG_VAR([target_configargs],
+ [additional configure arguments for target directories])
+
# For the build-side libraries, we just need to pretend we're native,
# and not use the same cache file. Multilibs are neither needed nor
# desired.
-build_configargs="--cache-file=../config.cache ${baseargs}"
+build_configargs="$build_configargs --cache-file=../config.cache ${baseargs}"
# For host modules, accept cache file option, or specification as blank.
case "${cache_file}" in
# Host dirs don't like to share a cache file either, horribly enough.
# This seems to be due to autoconf 2.5x stupidity.
-host_configargs="--cache-file=./config.cache ${extra_host_args} ${baseargs}"
+host_configargs="$host_configargs --cache-file=./config.cache ${extra_host_args} ${baseargs}"
-target_configargs=${baseargs}
+target_configargs="$target_configargs ${baseargs}"
# Passing a --with-cross-host argument lets the target libraries know
# whether they are being built with a cross-compiler or being built