many distutils tests fail when run from the installed location, either depending on the 'srcdir' macro, files not installed ('xxmodule.c'), or needing write permissions in the installed location.

Matthias, I think this is already fixed for Python 3.3 and later (at least.) There may still be problems in 2.7, but I'm not sure if it's worth fixing them there. Can you see if you still have problems, and if so, show us how to reproduce them? (Is it just 'python -m test.regrtest'? Is it just test_distutils or also other tests?)

three are still failing with 3.4:

cc-4.9.real: error: /tmp/tmpdjxmlia5/xx.cpython-34m.so: No such file or directory
gcc-4.9.real: error: /tmp/tmp4zpi6ktg/foo.cpython-34m.so: No such file or directory
gcc-4.9.real: error: build/lib.linux-x86_64-3.4/xx.cpython-34m.so: No such file or directory
test test_distutils failed -- multiple errors occurred; run in verbose mode for details
1 test failed:
    test_distutils


test_build_ext (distutils.tests.test_build_ext.BuildExtTestCase)
test_get_outputs (distutils.tests.test_build_ext.BuildExtTestCase)
test_record_extensions (distutils.tests.test_install.InstallTestCase)

The reason here is that the xx module is not found (where should it be installed in the installed testsuite?).

The xx module is built by the unit tests IIRC.

so the issue here is that -L -o <file> is passed to the compiler, and -o is interpreted as the library dir, and <file> as an input file.

To robustify, change distutils/tests/support.py to not include empty directory names.

To fix, change configure.ac (RUNPATH) not to unconditionally end the environment variables with an empty directory.

adding Ronald, Darwin is the only platform having quotes around this. Is this really needed/wanted?

The quotes that you removed around the DYLD_FRAMEWORK_PATH step are not needed, at least until the rest of configure.ac and Makefile.pre.in support paths with spaces et al.  However, you missed removing the single quotes around the DYLD_LIBRARY_PATH step here:

RUNSHARED='DYLD_LIBRARY_PATH=`pwd`${DYLD_LIBRARY_PATH:+:${DYLD_LIBRARY_PATH}}'

Otherwise, the patch LGTM; I tested it with --enable-framework and --enable-shared configs on OS X.

New changeset faef1da30c6d by doko in branch '2.7':
- Issue #17752: Fix distutils tests when run from the installed location.
http://hg.python.org/cpython/rev/faef1da30c6d

New changeset 7d1929cc08dd by doko in branch '3.3':
- Issue #17752: Fix distutils tests when run from the installed location.
http://hg.python.org/cpython/rev/7d1929cc08dd

New changeset 01e933cb1de9 by doko in branch '3.4':
- Issue #17752: Fix distutils tests when run from the installed location.
http://hg.python.org/cpython/rev/01e933cb1de9

New changeset c0bcf1383d77 by doko in branch 'default':
- Issue #17752: Fix distutils tests when run from the installed location.
http://hg.python.org/cpython/rev/c0bcf1383d77

For future fixes, please note that 3.3 is in security mode.

Can this issue be closed?

yes, noted myself (too late), and informed Georg about it. Closing for now.

nosy: + ronaldoussoren, ned.deily, hynek
messages: + msg218026

keywords: + patch

messages: + msg216514
versions: + Python 2.7, - Python 3.3, Python 3.4