[Python-bugs-list] [ python-Bugs-810263 ] incorrect "msvc 6.0 not found" error

[SourceForge.net]

Bugs item #810263, was opened at 2003-09-21 16:30
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=810263&group_id=5470

Category: Distutils
Group: Python 2.3
Status: Open
Resolution: None
Priority: 7
Submitted By: Guido van Rossum (gvanrossum)
Assigned to: Nobody/Anonymous (nobody)
Summary: incorrect "msvc 6.0 not found" error

Initial Comment:
I am trying to build a program (pylibpcap-0.4, but I

think it doesn't matter which program except for the

fact that it needs to compile a C extension) on Windows

XP (don't laugh, it's better than Windows 98 :-).  I've

installed MS VC 6.0 from CD, and run the vcvars32

script. When I run the setup.py script, I get the message



                   "Python was built with version 0.6

of Visual Studio, "

                   "and extensions need to be built

with the same "

                   "version of the compiler, but it

isn't installed."



from msvccompiler.py.



It is clearly mistaken. When I try Python 2.2, the

compiler is found just fine.



I'd like to see this fixed before 2.3.1 is released.



(I should note that I didn't install any service packs

for the compiler. Maybe the knowledge about registry

entries built into get_msvc_paths() is only correct for

later service packs?  Or for pre-XP? I can't find the

registry key ...\6.0\Build System\, which is looked for

by this function (the part up to and including ...\6.0\

exists); I do notice that the product directory is in

...\6.0\Products\Microsoft Visual C++\ProductDir, which

has the value C:\Program Files\Microsoft Visual

Studio\VC98, and that's where the compiler is installed

(the binaries are in the subdirectory "bin" there).



I do note that the code that raises the error was

installed by a patch that purported to improve VC 7.1

compatibility. Too bad it broke 6.0 compatibility

(especially since that is what we still currently use :-).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=810263&group_id=5470