[issue17752] many distutils tests fail when run from the installed location

Matthias Klose added the comment: yes, noted myself (too late), and informed Georg about it. Closing for now. -- resolution: -> fixed status: open -> closed ___ Python tracker _

[issue17752] many distutils tests fail when run from the installed location

Éric Araujo added the comment: For future fixes, please note that 3.3 is in security mode. Can this issue be closed? -- ___ Python tracker ___ __

[issue17752] many distutils tests fail when run from the installed location

Roundup Robot added the comment: 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 whe

[issue17752] many distutils tests fail when run from the installed location

Roundup Robot added the comment: 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 -- nosy: +python-dev ___ Python tracker

[issue17752] many distutils tests fail when run from the installed location

Ned Deily added the comment: 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: RUN

[issue17752] many distutils tests fail when run from the installed location

Changes by Matthias Klose : -- stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue17752] many distutils tests fail when run from the installed location

Matthias Klose added the comment: so the issue here is that -L -o is passed to the compiler, and -o is interpreted as the library dir, and 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 unc

[issue17752] many distutils tests fail when run from the installed location

Éric Araujo added the comment: The xx module is built by the unit tests IIRC. -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-

[issue17752] many distutils tests fail when run from the installed location

Matthias Klose added the comment: 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-3

[issue17752] many distutils tests fail when run from the installed location

Thomas Wouters added the comment: 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 'py

[issue17752] many distutils tests fail when run from the installed location

New submission from Matthias Klose: 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. -- components: Tests messages: 187068 nosy: doko prior