Changes between Version 1 and Version 2 of Ticket #38163, comment 4
- Timestamp:
- Nov 14, 2013, 2:17:10 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #38163, comment 4
v1 v2 1 Same problem as above. Earlier, editing portconfigure.tcl did the trick, but with the newer MacPorts I confirm that this does not fix it; i.e., error persists despite fresh clean/reinstall of MacPorts, rebuilding with -headerpad... in portconfigure.tcl 1 For future reference. I had begun posting "Same problem as above. Earlier, editing portconfigure.tcl did the trick, but with the newer MacPorts I confirm that this does not fix it; i.e., error persists despite fresh clean/reinstall of MacPorts, rebuilding with -headerpad... in portconfigure.tcl " 2 2 3 "As explained in your links, there is nothing py2app can do about this." 3 ...However, this is now... 4 4 5 RESOLVED: Posting solution for future users: 6 The issue resulted from my default python installation somehow getting switched from the MacPorts version in /opt/local/bin to the Apple version in /usr/bin. (No idea how. Lion->Mountain Lion upgrade, perhaps?) 5 7 6 So, what then? You're saying basically py27-py2app is ''broken'' and ''non-functional'' in MacPorts? Why then is it even still listed as an available port? Do users then just find the source elsewhere and compile 'by hand'? 8 MacPorts now comes with the required -headerpad,etc. modifications, so if you are still encountering the error that started this thread, run "which python" and if you see "/usr/bin/python", then set your path so that it checks /opt/local/bin first. 7 9 8 I don't understand how you can label this ticket as ''Invalid'' and Resolved if it's a mission-critical error that prevents the program from working at all... 10 With this change -- i.e., using the actual MacPorts python instead of the 'default' (duhhh) -- the build finishes successfully and the executable application runs without problem.