Committed, testsuite/lib/libstdc++.exp: Use AR and RANLIB, not AR_FOR_TARGET, RANLIB_FOR_TARGET.

[Hans-Peter Nilsson]

This is a partial fix or perhaps rather spinoff for PR 32499.
(When building a target library, the target tools counts as the
host, see RAW_CXX_TARGET_EXPORTS -> BASE_TARGET_EXPORTS in
toplevel/Makefile.in.  For GNU make and if you don't want to
override the command, it apparently doesn't make a difference;
*_FOR_TARGET had the values you want.  Not release critical.)

Suggested by Paolo Carlini and insisted by Rainer Orth (see
bugzilla), I believe this counts as obvious.  Sanity-checked by
x86_64-unknown-linux-gnu x cris-elf.

libstdc++-v3:
        * testsuite/lib/libstdc++.exp (v3-build_support): Use env(AR)
        and env(RANLIB), not env(AR_FOR_TARGET) and env(RANLIB_FOR_TARGET).

--- libstdc++.exp.prev	2007-05-09 07:48:28.000000000 +0200
+++ libstdc++.exp	2007-07-05 19:13:18.000000000 +0200
@@ -502,8 +502,8 @@ proc v3-build_support { } {
     }
 
     # Collect into libtestc++.a
-    if  [info exists env(AR_FOR_TARGET)] {
-	set ar $env(AR_FOR_TARGET)
+    if  [info exists env(AR)] {
+	set ar $env(AR)
     } else {
 	set ar [transform "ar"]
     }
@@ -512,8 +512,8 @@ proc v3-build_support { } {
     set result [lindex [local_exec "$arcommand" "" "" 300] 0]
     verbose "link result is $result"
     if { $result == 0 } {
-	if  [info exists env(RANLIB_FOR_TARGET)] {
-	    set ranlib $env(RANLIB_FOR_TARGET)
+	if  [info exists env(RANLIB)] {
+	    set ranlib $env(RANLIB)
 	} else {
 	    set ranlib [transform "ranlib"]
 	}

brgds, H-P