Issue 6022: test_distutils leaves a 'foo' file behind in the cwd

The test for issue #5977 added to test_get_outputs leaves a file named
'foo' behind in the current working directory.

done in r72636, r72637, r72638, r72639

After lets call it "cd temp dir" modification the fail on my linux box :
missing libpithon2.7.
What is the buildbot trick as the test pass on all linux buildbots ?

It's not just on the buildbots, it passes fine on my Gentoo box.  So the
question really is, what's different about your box that makes it fail?
 Can you figure out what bit of code is not finding that library?

How do you run the tests?  Maybe that makes a difference.

I think that one difference is build outside source tree. Not sure that
this is problem - the linker flags contain "... -L. -lpython2.7 ..." and
after change into another directory(temp) library is no more in current
directory.

Right now I'm too busy to look again into details.

Hi All,
The test always fails even builddir == srddir , with and without
directory links in src-/build-path. 

$ LD_LIBRARY_PATH=`pwd` ./python
Python 2.7a0 (trunk:73046M, May 30 2009, 14:09:06)
[GCC 4.2.4] on linux2
....

$ cat /tmp/pynexttest
test_distutils

The command to run test is:
$ LC_ALL=C ./python -E -tt ./Lib/test/regrtest.py -l -v -s

P.S.: the test command start with LD_LIBRARY_PATH=`pwd`

see issue 8335

messages: + msg87760
components: + Distutils
versions: + Python 2.6, Python 3.0, Python 3.1, Python 2.7

nosy: + tarek