Explain what's probably a problem unique to Win9x in building _ssl.

This commit is contained in:
Tim Peters 2002-12-04 03:16:37 +00:00
parent e8bcb25fbd
commit 6ee68d20b7
1 changed files with 27 additions and 0 deletions

View File

@ -226,6 +226,8 @@ _ssl
the build. This Python script locates and builds your OpenSSL
installation, then invokes a simple makefile to build the final .pyd.
Win9x users: see "Win9x note" below.
build_ssl.py attempts to catch the most common errors (such as not
being able to find OpenSSL sources, or not being able to find a Perl
that works with OpenSSL) and give a reasonable error message.
@ -237,6 +239,31 @@ _ssl
build_ssl.py/MSVC isn't clever enough to clean OpenSSL - you must do
this by hand.
Win9x note: If, near the start of the build process, you see
something like
C:\Code\openssl-0.9.6g>set OPTS=no-asm
Out of environment space
then you're in trouble, and will probable also see these errors near
the end of the process:
NMAKE : fatal error U1073: don't know how to make
'crypto\md5\asm\m5_win32.asm'
Stop.
NMAKE : fatal error U1073: don't know how to make
'C:\Code\openssl-0.9.6g/out32/libeay32.lib'
Stop.
You need more environment space. Win9x only has room for 256 bytes
by default, and especially after installing ActivePerl (which fiddles
the PATH envar), you're likely to run out. KB Q230205
http://support.microsoft.com/default.aspx?scid=KB;en-us;q230205
explains how to edit CONFIG.SYS to cure this.
YOUR OWN EXTENSION DLLs
-----------------------
If you want to create your own extension module DLL, there's an example