-Mayby checking if ssh works in this way is not the best idea?

Changed files:
    mpich-fuckssh.patch -> 1.1

diff --git a/mpich-fuckssh.patch b/mpich-fuckssh.patch
new file mode 100644 (file)
index 0000000..6343f7d
--- /dev/null
+++ b/mpich-fuckssh.patch
@@ -0,0 +1,38 @@
+diff -urN mpich-1.2.1/mpid/ch_p4/configure mpich-1.2.1-new/mpid/ch_p4/configure
+--- mpich-1.2.1/mpid/ch_p4/configure   Tue Aug 22 21:36:07 2000
++++ mpich-1.2.1-new/mpid/ch_p4/configure       Tue Mar 20 01:53:37 2001
+@@ -1140,6 +1140,7 @@
+   ;;
+ esac
+ fi
++set -x
+ RSHCOMMAND="$ac_cv_path_RSHCOMMAND"
+ if test -n "$RSHCOMMAND"; then
+   echo "$ac_t""$RSHCOMMAND" 1>&1
+@@ -1148,25 +1149,12 @@
+ fi
+ 
+         if test -n "$RSHCOMMAND" ; then
+-          echo $ac_n "checking whether $RSHCOMMAND works""... $ac_c" 1>&1
+-echo "configure:1153: checking whether $RSHCOMMAND works" >&2
+-            output=`$RSHCOMMAND $machine -n true 2>&1`
+-            if test -n "$output" ; then
+-              echo "$ac_t""no" 1>&1
+-              echo "Errors while trying to run true on $machine with $program"
+-              echo "$output"
+-              RSHCOMMAND=""
+-              # HORRIBLE, TERRIBLE BUG in AUTOCONF!!!
+-              # It is determined to INCORRECTLY remember some results,
+-              # while forgetting others (like "cross-compiling")
+-              unset ac_cv_path_RSHCOMMAND
+-            else
+               echo "$ac_t""yes" 1>&1
+               break
+-          fi
+         fi
+     done
+ fi
++set +x
+ if test -z "$RSHCOMMAND" ; then
+     echo "configure: warning: You must use the secure server to start programs" 1>&2
+ fi