This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
[toplevel patch] Remove future variable name conflict in configure.in
- From: Nathanael Nerode <neroden at twcny dot rr dot com>
- To: gcc-patches at gcc dot gnu dot org, binutils at sources dot redhat dot com, gdb-patches at sources dot redhat dot com
- Date: Thu, 26 Jun 2003 13:24:26 -0400
- Subject: [toplevel patch] Remove future variable name conflict in configure.in
This is the only variable name conflict with config-lang.in fragments.
It turns out that target_libs isn't used after its late assignment
from the config-lang.in fragments, which makes the assignment worthless,
so I just deleted it.
Tested on i686-pc-linux-gnu.
This is the precursor to simply sourcing the config-lang.in fragments
at the top level rather than running them through ungodly sed expressions.
* configure.in: Rename 'target_libs' to 'target_libraries'.
Remove useless reference to 'target_libs'.
* configure: Regenerate.
Index: configure.in
===================================================================
RCS file: /cvs/gcc/gcc/configure.in,v
retrieving revision 1.241
diff -u -r1.241 configure.in
--- configure.in 23 Jun 2003 00:42:54 -0000 1.241
+++ configure.in 26 Jun 2003 17:19:29 -0000
@@ -136,7 +136,7 @@
# these libraries are built for the target environment, and are built after
# the host libraries and the host tools (which may be a cross compiler)
#
-target_libs="target-libiberty \
+target_libraries="target-libiberty \
target-libgloss \
target-newlib \
target-libstdc++-v3 \
@@ -144,10 +144,10 @@
${libgcj} \
target-libobjc"
-# these tools are built using the target libs, and are intended to run only
-# in the target environment
+# these tools are built using the target libraries, and are intended to
+# run only in the target environment
#
-# note: any program that *uses* libraries that are in the "target_libs"
+# note: any program that *uses* libraries that are in the "target_libraries"
# list belongs in this list. those programs are also very likely
# candidates for the "native_only" list which follows
#
@@ -162,7 +162,7 @@
## ${target_configdirs} is directories we build using the target tools.
#
configdirs=`echo ${host_libs} ${host_tools}`
-target_configdirs=`echo ${target_libs} ${target_tools}`
+target_configdirs=`echo ${target_libraries} ${target_tools}`
# Only make build modules if build != host.
# This should be done more generally, but at the moment it doesn't matter.
@@ -805,7 +805,7 @@
*) add_this_lang=no ;;
esac
if test x"${add_this_lang}" = xyes; then
- eval target_libs='"$target_libs "'\"$this_lang_libs\"
+ :
else
eval noconfigdirs='"$noconfigdirs "'\"$this_lang_libs $this_lang_dirs\"
fi