[issue9558] build_ext fails on VS8.0

Éric Araujo added the comment: Fixed in [4f2da1ec00a2] (distutils2), r87280 (3.2), r87201 (3.1), r87282 (2.7). Thanks to you both. -- resolution: accepted -> fixed stage: -> committed/rejected status: pending -> closed ___ Python tracker

[issue9558] build_ext fails on VS8.0

Éric Araujo added the comment: Thanks for the ping and the confirmation that it works. Will check in shortly. -- components: +Distutils2 priority: normal -> high status: open -> pending versions: +3rd party -Python 2.6 ___ Python tracker

[issue9558] build_ext fails on VS8.0

Amaury Forgeot d'Arc added the comment: I happen to have the same change in my workspace. Please apply this patch, it fixes the test suite when compiled with VS8.0. -- nosy: +amaury.forgeotdarc ___ Python tracker

[issue9558] build_ext fails on VS8.0

Hirokazu Yamamoto added the comment: Won't this go into python3.2? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue9558] build_ext fails on VS8.0

R. David Murray added the comment: Éric, 'release blocker' policy depends on the release manager :) Barry, for example, likes people to set release blocker on issues they want him to make sure he looks at before the release. The release manager can always knock it down. As can other develo

[issue9558] build_ext fails on VS8.0

Changes by Éric Araujo : -- nosy: +christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue9558] build_ext fails on VS8.0

Changes by Antoine Pitrou : -- assignee: tarek -> eric.araujo resolution: -> accepted ___ Python tracker ___ ___ Python-bugs-list mail

[issue9558] build_ext fails on VS8.0

Hirokazu Yamamoto added the comment: > Does test_build_ext pass? Here are results. py26 is calling python_d.exe built with VS8.0. I installed VS8.0 very recently, so I'm not familier with historical reason. ;-) # Translate error message into English... # LINK : fatal error LNK1104: cannot open

[issue9558] build_ext fails on VS8.0

Éric Araujo added the comment: Digging into the history of build_ext, I see that you committed a fix for VC 6 two years ago, so I think you’re more knowledgeable than me. I’m adding a Windows expert for confirmation. Going back to 2007 finds the origin of the line you’re editing: “[svn r59290

[issue9558] build_ext fails on VS8.0

Hirokazu Yamamoto added the comment: Yes, I can confirm the same bug on Python3.2 and others. The reason is LIBPATH includes not "PC/VS8.0" but "PC/VS8.0/win32release" which doesn't exist. I hope attached patch will fix this issue. -- ___ Python tr

[issue9558] build_ext fails on VS8.0

Éric Araujo added the comment: Thank you for the report. “release blocker” is a bit strong here, usually it’s set by release managers themselves or by people having their agreement (unless I’m mistaken). Does “python -m distutils.test.test_build_ext” pass? Do yo have tested your bug with rec

[issue9558] build_ext fails on VS8.0

Hirokazu Yamamoto added the comment: Is *release blocker* too strong? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue9558] build_ext fails on VS8.0

New submission from Hirokazu Yamamoto : test_build_ext fails on VS8.0. == ERROR: test_build_ext (distutils.tests.test_build_ext.BuildExtTestCase) -- Traceback