X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=README.win32;h=5499d3a4f4548af5cf81c192b02e232f9b17bff2;hb=1b1e14d34a33bfe0df591910cafcab54421ca8a8;hp=37df1d4088039c865bce2941e33e138f5aa76d39;hpb=5db1039675bdeda8d9e4e8a1462abefb8ede0419;p=p5sagit%2Fp5-mst-13.2.git diff --git a/README.win32 b/README.win32 index 37df1d4..5499d3a 100644 --- a/README.win32 +++ b/README.win32 @@ -90,7 +90,7 @@ work for MakeMaker builds.) A port of dmake for win32 platforms is available from: - ftp://ftp.linux.activestate.com/pub/staff/gsar/dmake-4.1-win32.zip + http://cpan.perl.org/authors/id/GSAR/dmake-4.1pl1-win32.zip (This is a fixed version of original dmake sources obtained from http://www.wticorp.com/dmake/. As of version 4.1PL1, the original @@ -121,9 +121,9 @@ GCC-2.95.2 binaries can be downloaded from: The GCC-2.95.2 bundle comes with Mingw32 libraries and headers. -Make sure you install the binaries as indicated in the README for -the GCC bundle. You may need to set up a few environment variables -(usually run from a batch file). +Make sure you install the binaries that work with MSVCRT.DLL as indicated +in the README for the GCC bundle. You may need to set up a few environment +variables (usually run from a batch file). You also need dmake. See L above on how to get it. @@ -177,7 +177,7 @@ If you have either the source or a library that contains des_fcrypt(), enable the appropriate option in the makefile. des_fcrypt() is not bundled with the distribution due to US Government restrictions on the export of cryptographic software. Nevertheless, this routine -is part of the "libdes" library (written by Ed Young) which is widely +is part of the "libdes" library (written by Eric Young) which is widely available worldwide, usually along with SSLeay (for example: "ftp://fractal.mta.ca/pub/crypto/SSLeay/DES/"). Set CRYPT_SRC to the name of the file that implements des_fcrypt(). Alternatively, if @@ -215,21 +215,6 @@ The build process may produce "harmless" compiler warnings (more or less copiously, depending on how picky your compiler gets). The maintainers are aware of these warnings, thankyouverymuch. :) -When building using Visual C++, a perl95.exe will also get built. This -executable is only needed on Windows95, and should be used instead of -perl.exe, and then only if you want sockets to work properly on Windows95. -This is necessitated by a bug in the Microsoft C Runtime that cannot be -worked around in the "normal" perl.exe. perl95.exe gets built with its -own private copy of the C Runtime that is not accessible to extensions -(which see the DLL version of the CRT). Be aware, therefore, that this -perl95.exe will have esoteric problems with extensions like perl/Tk that -themselves use the C Runtime heavily, or want to free() pointers -malloc()-ed by perl. - -You can avoid the perl95.exe problems completely if you either enable -USE_PERLCRT with Visual C++, or use Borland C++ for building perl. In -those cases, perl95.exe is not needed and will not be built. - =back =head2 Testing @@ -250,10 +235,6 @@ default path. You will need to copy the DLLs reported by the messages from where Borland chose to install it, into the Windows system directory (usually somewhere like C:\WINNT\SYSTEM32), and rerun the test. -The Visual C runtime apparently has a bug that causes posix.t to fail -test#2. This usually happens only if you extracted the files in text -mode. Enable the USE_PERLCRT option in the Makefile to fix this bug. - Please report any other failures as described under L. =head2 Installation