OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

Browse Source 
* 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
This commit is contained in:
DJ Delorie 2008-05-30 15:19:45 -04:00 committed by DJ Delorie
parent 856905c263
commit 97c3860d80
2 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
View File

@ -1,3 +1,8 @@
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.

5
gcc/exec-tool.in
View File

@ -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