exec-tool.in: Use an environment variable (private) instead of a file (shared) as a semaphore...

* exec-tool.in: Use an environment variable (private) instead of a
file (shared) as a semaphore, so as to not break parallel builds.

From-SVN: r136221

gcc/ChangeLog

+2008-05-30  DJ Delorie  <dj@redhat.com>
+
+	* exec-tool.in: Use an environment variable (private) instead of a
+	file (shared) as a semaphore, so as to not break parallel builds.
+
 2008-05-30  Steven Bosscher  <stevenb.gcc@gmail.com>
 
 	* optabs.c (maybe_encapsulate_block): Remove.

gcc/exec-tool.in

@@ -61,12 +61,11 @@ case "$original" in
       # libtool has not relinked ld-new yet, but we cannot just use the
       # previous stage (because then the relinking would just never happen!).
       # So we take extra care to use prev-ld/ld-new *on recursive calls*.
-      test -f $lt_prog-recursive && exec $scriptdir/../prev-$dir/$prog ${1+"$@"}
+      test x"$LT_RCU" = x"1" && exec $scriptdir/../prev-$dir/$prog ${1+"$@"}
 
-      touch $lt_prog-recursive
+      LT_RCU=1; export LT_RCU
       $scriptdir/../$dir/$prog ${1+"$@"}
       result=$?
-      rm -f $lt_prog-recursive
       exit $result
 
     else