classification
Title: VS9.0 build doesn't work
Type: compile error Stage:
Components: Build, Windows Versions: Python 3.3
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: loewis, pitrou, python-dev, skrah
Priority: high Keywords:

Created on 2012-06-14 19:33 by pitrou, last changed 2012-06-14 20:34 by loewis. This issue is now closed.

Messages (4)
msg162816 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2012-06-14 19:33
When I try to launch the AMD64 debug build:

Z:\default>PC\VS9.0\amd64\python_d.exe

I get an error box complaining that "python33_d.dll" is missing from my system.

Indeed it doesn't seem there:

Z:\default>dir PC\VS9.0\amd64\*.dll
 Volume in drive Z is VBOX_cpython
 Volume Serial Number is 0000-0805

 Directory of Z:\default\PC\VS9.0\amd64

05/16/2012  02:09 PM         3,176,960 python33.dll
05/16/2012  02:08 PM            79,872 python3.dll
               2 File(s)      3,256,832 bytes
               0 Dir(s)  60,807,380,992 bytes free
msg162818 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2012-06-14 19:40
Ah, apparently it's a linking error and it doesn't work for release builds either:

1>   Creating library Z:\default\PC\VS9.0\\amd64\python33.lib and object Z:\default\PC\VS9.0\\amd64\python33.exp
1>timemodule.obj : error LNK2019: unresolved external symbol _PyNamespace_New referenced in function time_get_clock_info
1>sysmodule.obj : error LNK2001: unresolved external symbol _PyNamespace_New
1>object.obj : error LNK2001: unresolved external symbol _PyNamespace_Type
1>Z:\default\PC\VS9.0\\amd64\\python33.dll : fatal error LNK1120: 2 unresolved externals
msg162819 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2012-06-14 19:54
New changeset ccbf6f970943 by Antoine Pitrou in branch 'default':
Issue #15070: fix VS9.0 build regression
http://hg.python.org/cpython/rev/ccbf6f970943
msg162824 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2012-06-14 20:34
The question really remains whether the VS 9 project files should be generated from the VS 2010 ones; this would have resolved this error as well (even though Richard Oudkerk probably wouldn't have run those generators - consequentially, the older project files are still broken).

In any case, I still think that breakage of the VS9 build shouldn't have high priority. Instead, contributors really should get a copy of VS 2010 express - they will need it until at least 2015.
History
Date User Action Args
2012-06-14 20:34:49loewissetmessages: + msg162824
2012-06-14 19:55:07pitrousetstatus: open -> closed
resolution: fixed
2012-06-14 19:54:21python-devsetnosy: + python-dev
messages: + msg162819
2012-06-14 19:40:46pitrousetpriority: normal -> high

messages: + msg162818
title: AMD64 debug VS9.0 build doesn't work -> VS9.0 build doesn't work
2012-06-14 19:33:50pitroucreate