This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/32499] libstdc++ testsuite fails on platforms without ranlib
- From: "hp at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Jul 2007 17:28:08 -0000
- Subject: [Bug libstdc++/32499] libstdc++ testsuite fails on platforms without ranlib
- References: <bug-32499-81@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from hp at gcc dot gnu dot org 2007-07-05 17:28 -------
In reply to comment #6, about the FOR_TARGET: ok, I see, and I also see I
mentioned in
<http://gcc.gnu.org/ml/gcc-patches/2007-03/msg00694.html> that the plain AR,
RANLIB worked. Nevertheless, I'm testing the following patch for my setup:
--- 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"]
}
and you'll have to fix the ":" problem separately.
Unless you prefer a 'set ranlib "$env(SHELL) -c $env(RANLIB)"' but that looks
a little bit too gross.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32499