wasm-demo/demo/ermis-f/python_m/cur/0670

46 lines
1.7 KiB
Plaintext

From: tim_one at email.msn.com (Tim Peters)
Date: Sun, 11 Apr 1999 00:44:03 GMT
Subject: 1.5.2c1 will not compile on Windows NT SP4 with VC++ 6.0 SP1
In-Reply-To: <923765974.19722.0.nnrp-03.9e982a40@news.demon.co.uk>
References: <923765974.19722.0.nnrp-03.9e982a40@news.demon.co.uk>
Message-ID: <000001be83b4$65c95d80$7fa22299@tim>
Content-Length: 1368
X-UID: 670
[Barry Scott, reports several weird problems trying to build 1.5.2c1 under
VC 6 on NT]
Barry, you didn't say how you *started* your build, but I suspect you
followed the instructions in PC\readme.txt without reading the first
paragraph:
(NOTE: the project files for MS VC++ 5.x are now in the PCbuild
directory. See the file readme.txt there for instructions.)
If so, throw out everything you did, and start over in the PCbuild
directory, where a full-blown .dsw file awaits your building pleasure.
Had no problems building either release or debug Pythons starting from
there, under Win95 using VC 5. I doubt VC 6 or NT have anything to do with
what you're seeing, since e.g. the reopmodule.c you report a complaint about
is mentioned only in the PC directory, not in the (correct) PCbuild
directory.
Note: I did not attempt to build _tkinter.
i-try-to-be-helpful-but-ain't-masochistic<wink>-ly y'rs - tim
PS to Guido: A fellow at work tripped over much the same thing when
building one of the 1.5.2bx releases. I figured the odds of somebody else
skipping over the first paragraph of the PC readme too were so slim that it
wasn't worth reporting. The problem may be that an experienced Windows-head
decides to start partying the instant they see the PC\vc40.mak file (which,
I believe, tries to do all the obsolete stuff Barry reported)!