[issue4151] Separate build dir broken

Éric Araujo added the comment: For the record, I’m not clear about what is fixed or not in each branch. -- ___ Python tracker ___ ___

[issue4151] Separate build dir broken

Éric Araujo added the comment: I think so too. -- assignee: nascheme -> mwh nosy: +mwh resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue4151] Separate build dir broken

Neil Schemenauer added the comment: I believe the latest problem reported has been fixed by SVN rev 80649. -- assignee: -> nascheme nosy: -nas stage: -> committed/rejected ___ Python tracker

[issue4151] Separate build dir broken

Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue4151] Separate build dir broken

Matthias Klose added the comment: current status with 2.7 alpha3: FAIL: test_get_python_inc (distutils.tests.test_sysconfig.SysconfigTestCase) -- Traceback (most recent call last): File "/home/packages/python/2.7/python2.7-2

[issue4151] Separate build dir broken

Roumen Petrov added the comment: One additional commit change srcdir = os.path.normpath(srcdir) to srcdir = os.path.abspath(srcdir) and this should not create relative path. In this case I expect build in directory build/temp./. Andi, did above change work for you. ___

[issue4151] Separate build dir broken

Andy Buckley added the comment: I'm having trouble with this as well :( It's pretty much a blocker for integrating distutils-based extension builds with an autotools library build, because the "make distcheck" target explicitly does the build in a subtree of the source directory, and write-prot

[issue4151] Separate build dir broken

Neil Schemenauer added the comment: On Thu, Feb 12, 2009 at 01:32:37PM +, Matthias Klose wrote: > still seen on the 2.6 branch. applying r69374 on the branch doesn't fix > it there. The fix is spread over a number of commits: r69374, r69322, r69315, r69305, r69304, r69303, r69302. It could

[issue4151] Separate build dir broken

Matthias Klose added the comment: still seen on the 2.6 branch. applying r69374 on the branch doesn't fix it there. -- nosy: +doko resolution: fixed -> status: closed -> open versions: +Python 2.6 ___ Python tracker

[issue4151] Separate build dir broken

Neil Schemenauer added the comment: Roumen, thanks for reporting the bug. It seems that distutils requires an absolute path (although I didn't waste time digging too deep into the issue). ___ Python tracker ___

[issue4151] Separate build dir broken

Roumen Petrov added the comment: The "clean build' mean missing subdirectory build in . Now module objects go in build/Modules/. I guess that second make succeed as libffi create build directory. ___ Python tracker ___

[issue4151] Separate build dir broken

Roumen Petrov added the comment: May be not related to the commit but after clean make fail to build a number of modules, as example _bisect. Second run of make build all left. The value of srcdir (from Makefile) is ".." without quotes. About cleanup: one use of '(srcdir,)==...' left in setup

[issue4151] Separate build dir broken

Changes by Neil Schemenauer : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/pyth

[issue4151] Separate build dir broken

Neil Schemenauer added the comment: I committed my proposed changes in several chunks, ending with r69305. I think building in a separate directory again works and that non-POSIX platforms are not adversely affected by this change. -- nosy: +nascheme resolution: -> fixed status: open

[issue4151] Separate build dir broken

Neil Schemenauer added the comment: I committed my proposed changes in several chunks, ending with r69305. I think building in a separate directory again works and that non-POSIX platforms are not adversely affected by this change. ___ Python tracker

[issue4151] Separate build dir broken

Neil Schemenauer <[EMAIL PROTECTED]> added the comment: [Roumen Petrov] > Modification for test_build_ext.py from above mentioned issue break > non-posix builds. Without that change the test fails on Unix platforms when the build is not done inside the source directory. I guess the problem must

[issue4151] Separate build dir broken

Roumen Petrov <[EMAIL PROTECTED]> added the comment: get_python_inc() and test case is addressed in issue4070 as well. -- nosy: +rpetrov ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4151] Separate build dir broken

Changes by Neil Schemenauer <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file11839/get_python_inc2.patch ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue4151] Separate build dir broken

Changes by Neil Schemenauer <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11837/get_python_inc.patch ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4151] Separate build dir broken

Changes by Neil Schemenauer <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file11838/get_python_inc2.patch ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue4151] Separate build dir broken

New submission from Neil Schemenauer <[EMAIL PROTECTED]>: Building in a separate directory got broken at some point. The code is hairy but it looks like the source of the problem was a lame sysconfig.get_python_inc() function. The attached patches fix things and hopefully do not introduce any n