[issue15772] Unresolved symbols in Windows 64-bit python

2012-10-22 Thread Martin v . Löwis
Martin v. Löwis added the comment: Closing as works-for-me then. -- resolution: - works for me status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15772 ___

[issue15772] Unresolved symbols in Windows 64-bit python

2012-10-21 Thread Silverback Networks
Silverback Networks added the comment: Boy, do I feel like an idiot now. An update to VC 2010 Express SP1 had clobbered by x64 build capabilities completely, and even reinstalling the SDK did nothing. It turns out that there's a specific hotfix you have to install to get x64 builds working

[issue15772] Unresolved symbols in Windows 64-bit python

2012-10-20 Thread Silverback Networks
Silverback Networks added the comment: Same errors in 3.3. Some names are decorated, some aren't, seemingly at random. For instance, python32.lib contains: 35B20 _PyObject_Dump 35B20 __imp__PyObject_Dump and just below that, 2924A PyObject_Free 2924A __imp_PyObject_Free But

[issue15772] Unresolved symbols in Windows 64-bit python

2012-10-20 Thread Silverback Networks
Changes by Silverback Networks silverback...@gmail.com: -- versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15772 ___ ___

[issue15772] Unresolved symbols in Windows 64-bit python

2012-08-23 Thread Saul Spatz
New submission from Saul Spatz: In trying to build a SWING module on Windows with 64-bit python, I get the linker errors listed at the bottom of this message. I have this problem with both python 2.7 and 3.2. I have built the project without problems on Windows with 32-bit python, and a

[issue15772] Unresolved symbols in Windows 64-bit python

2012-08-23 Thread Brian Curtin
Changes by Brian Curtin br...@python.org: -- components: +Build nosy: +brian.curtin, loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15772 ___