From: guido at CNRI.Reston.VA.US (Guido van Rossum)
Date: Sat, 10 Apr 1999 14:51:06 -0400
Subject: 1.5.2c1 will not compile on Windows NT SP4 with VC++ 6.0 SP1
In-Reply-To: Your message of "Sat, 10 Apr 1999 18:42:10 BST."
             <000001be8379$76536190$060110ac@barrynt.private> 
References: <000001be8379$76536190$060110ac@barrynt.private> 
Message-ID: <199904101851.OAA04654@eric.cnri.reston.va.us>
Content-Length: 2558
X-UID: 82                                                  

> I extracted the 1.5.2c1 kit into P:\

Where did you get it?

> python15 error
> --------------------
> VC++ 6.0 gives this error.
> 
> Fatal error C1083: Cannot open source file:
> 'P:\Python-1.5.2c1\Modules\reopmodule.c': No such file or directory
> 
> The file reopmodule.c is not in the kit.

Hm...  I just tried this with VC++ 6.0 (not sure which service pack)
and there's no mention of reopmodule.c -- indeed that module was
deleted ages ago.

Where exactly did you get the project file you used?  Perhaps you had
an older project file (e.g. from an earlier alpha or beta release)
lying around?

> Having removed reopmodule.c from the project I get a link error
> 
> LINK : fatal error LNK1104: cannot open file ".\PC\python_nt.def"
> 
> This file is also missing.

This file is no longer distributed.  If you use the project files for
VC++ 5.0 that are distributed in the PCbuild directory (VC++  6.0 will 
convert them for you) you will note that it is no longer referenced.

> Removing python_nt.def from the project reveals files that need to be added
> to the project:
> 
>     object\bufferobject.c
>     pc\initwinsound.c
>     modules\_localemodule.c
> 
> LINK needs winmm.lib added to it.

These things have all been corrected in the distributed project files.

> Now I get a python15 built.
> 
> pyhon error
> ----------------
> The project cannot find python.c
> 
> fatal error C1083: Cannot open source file:
> 'P:\Python-1.5.2c1\python\Modules\python.c': No such file or directory
> 
> There is a extra "python" directory that is not in the kits layout.
> Fixed by replacing with 'P:\Python-1.5.2c1\Modules\python.c'
> 
> Same path problem with python15.lib.
> Fixed by replacing with P:\Python-1.5.2c1\vc40\python15.lib
> 
> Now I get a python.exe

Again, I wonder where you got the kit...

> _tkinter
> ----------
> The tk and tcl libs are named tk80.lib and tcl80.lib not tk80vc.lib and
> tcl80vc.lib.

Ditto -- your kit is not the set of workspace/project files I'm
distributing.  (Unless I've accidentally distributed two sets.  Which
set are you using?)

> I used the Tcl/Tk that the 1.5.2c1 installation put on my system.
> 
> Now I have _tkinter.dll
> 
> How was the kit for Windows built given all the missing or misnamed files?
> Or is this a side effect of using VC++ 6.0?
> 
> I also notice that the python.exe was built 8 apr 1999 but report sa dated
> of 12 Mar 1999
> on the interactive command line.

Sounds like you have an old Python build lying around.

--Guido van Rossum (home page: http://www.python.org/~guido/)




