Spurious make check failures due to automounter interaction

[Jeffrey A Law]

  In message < 13950.48609.979360.723560@xayide.TechFak.Uni-Bielefeld.DE >you wri
te:
  > When I run make check against egcs built from current CVS sources on
  > Digital UNIX V4.0B, I get some spurious failures.
  > 
  > >From gcc/testsuite/gcc.log:
  > 
  > Executing on host: /tmp/egcs/gcc/xgcc -B/tmp/egcs/gcc/ /amnt/pharao/volumes
  > /c3t3d0s5/egcs/src/egcs/egcs/egcs/gcc/testsuite/gcc.c-torture/compile/92072
  > 9-1.c  -w  -O2   -c  -o /tmp/egcs/gcc/testsuite/920729-1.o   
  > spawn /tmp/egcs/gcc/xgcc -B/tmp/egcs/gcc/ /amnt/pharao/volumes/c3t3d0s5/egc
  > s/src/egcs/egcs/egcs/gcc/testsuite/gcc.c-torture/compile/920729-1.c -w -O2 
  > -c -o /tmp/egcs/gcc/testsuite/920729-1.o 
  > xgcc: /amnt/pharao/volumes/c3t3d0s5/egcs/src/egcs/egcs/egcs/gcc/testsuite/g
  > cc.c-torture/compile/920729-1.c: No such file or directory
  > xgcc: No input files
  > compiler exited with status 1
  > output is:
  > xgcc: /amnt/pharao/volumes/c3t3d0s5/egcs/src/egcs/egcs/egcs/gcc/testsuite/g
  > cc.c-torture/compile/920729-1.c: No such file or directory
  > xgcc: No input files
  > 
  > FAIL: gcc.c-torture/compile/920729-1.c,  -O2  
  > 
  > while xgcc had no problem at all finding all previous source files.  The
  > problem is that the check-gcc target in gcc/Makefile (and some others, too)
  > use
  > 
  > 	srcdir=`cd ${srcdir}; pwd` ; export srcdir ; \
  > 
  > In the presence of (non-autofs) automounters, the resulting pathname is
  > likely to become invalid once amd unmounts the underlying filesystem, which
  > it may do, since no accesses via the amd-supported path (/vol/egcs instead
  > of /amnt/...) have taken place for some time.
  > 
  > Why is this cd/pwd construct used all, instead of just
  > 
  > 	export ${srcdir}
  > 
  > Isn't ${srcdir} guaranteed to be an absolute pathname anyway?
No srcdir it is not guaranteed to be an absolute pathname.

jeff