VS9.0 build doesn't work

[pitrou]

BPO	15070
Nosy	@loewis, @pitrou, @skrah

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2012-06-14.19:55:07.070>
created_at = <Date 2012-06-14.19:33:50.316>
labels = ['build', 'OS-windows']
title = "VS9.0 build doesn't work"
updated_at = <Date 2012-06-14.20:34:49.215>
user = 'https://github.com/pitrou'

bugs.python.org fields:

activity = <Date 2012-06-14.20:34:49.215>
actor = 'loewis'
assignee = 'none'
closed = True
closed_date = <Date 2012-06-14.19:55:07.070>
closer = 'pitrou'
components = ['Build', 'Windows']
creation = <Date 2012-06-14.19:33:50.316>
creator = 'pitrou'
dependencies = []
files = []
hgrepos = []
issue_num = 15070
keywords = []
message_count = 4.0
messages = ['162816', '162818', '162819', '162824']
nosy_count = 4.0
nosy_names = ['loewis', 'pitrou', 'skrah', 'python-dev']
pr_nums = []
priority = 'high'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = 'compile error'
url = 'https://bugs.python.org/issue15070'
versions = ['Python 3.3']

[pitrou]

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

[pitrou]

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

[python-dev]

New changeset ccbf6f970943 by Antoine Pitrou in branch 'default':
Issue bpo-15070: fix VS9.0 build regression
http://hg.python.org/cpython/rev/ccbf6f970943

[loewis]

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.