[issue1613] Makefile's VPATH feature is broken

Christian Heimes added the comment: Fixed in r59482 I've updated the README and changed distutils slightly. Distutils was using Modules/Setup.dist to detect an uninstalled Python. However Setup.dist is only available in the srcdir and not in the VPATH dir. I've changed it to Setup.local. ---

[issue1613] Makefile's VPATH feature is broken

Christian Heimes added the comment: Guido van Rossum wrote: > Do you need more help at this point? No, I'm fine. I've a working solution for the problem. :) Christian __ Tracker <[EMAIL PROTECTED]> _

[issue1613] Makefile's VPATH feature is broken

Guido van Rossum added the comment: Do you need more help at this point? __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe

[issue1613] Makefile's VPATH feature is broken

Christian Heimes added the comment: You are right! :) A make clean in the root of my local workspace solved the problem but revealed another problem: $ make running build running build_ext building '_struct' extension gcc -pthread -fPIC -fno-strict-aliasing -g -Wall -Wstrict-prototypes -I. -I/ho

[issue1613] Makefile's VPATH feature is broken

Guido van Rossum added the comment: Before I try to reproduce this, I remember having problems when switching between using VPATH and not using it in the same subversion workspace. The .o files left behind by one version confuse the other. -- nosy: +gvanrossum _

[issue1613] Makefile's VPATH feature is broken

New submission from Christian Heimes: Makefile has a feature called VPATH that is often used for cross platform compilation or the creation of a different flavor. Example: $ cd py3k $ mkdir debug $ cd debug $ ../configure --with-pydebug $ make ... gcc -pthread -c -fno-strict-aliasing -g -Wall -