Architecture of executable stub not always chosen correctly about py2app

[ronaldoussoren]

Original comment by Ronald Oussoren (Bitbucket: ronaldoussoren, GitHub: ronaldoussoren).

---

The architecture used is the one reported by "distutils.util.get_platform()", which works fine with all build variants that I've tried.

Which configure flags did you use to build Python?

[ronaldoussoren]

Original comment by Ronald Oussoren (Bitbucket: ronaldoussoren, GitHub: ronaldoussoren).

---

I still have no idea how to reproduce the issue and will close this issue next monday unless you can provide more information.

[ronaldoussoren]

Original comment by Anonymous.

---

To reproduce it, you need to somehow compile and install a 32-bit framework build of Python on a nominally 64-bit machine.

The way I did it was to set the CC environment variable to "gcc -m32" before compiling Python.

To check whether that has worked, do

% file /Library/Frameworks/Python.framework/Versions/X.Y/Python

It should say

/Library/Frameworks/Python.framework/Versions/2.7/Python: Mach-O dynamically linked shared library i386

If you then build an app with py2app using this build, the resulting app won't launch, because py2app puts in the x86_64 version of the executable stub.

[ronaldoussoren]

I'm not going to fix this one:

1. 32-bit code is no longer relevant on macOS
2. This should be fixed in CPython, in particular in the implementation of sysconfig.get_platform()