Update Changes; update Configure.

[p5sagit/p5-mst-13.2.git] / README.win32

diff --git a/README.win32 b/README.win32
index 834c64e..e9c56a0 100644 (file)
--- a/README.win32
+++ b/README.win32
@@ -192,7 +192,8 @@ Make sure you are in the "win32" subdirectory under the perl toplevel.
 This directory contains a "Makefile" that will work with
 versions of nmake that come with Visual C++ or the Platform SDK, and
 a dmake "makefile.mk" that will work for all supported compilers.  The
-defaults in the dmake makefile are setup to build using the GCC compiler.
+defaults in the dmake makefile are setup to build using Microsoft Visual
+C++ 6.0 or newer.
 
 =item *
 
@@ -253,16 +254,6 @@ the testsuite (many tests will be skipped).
 There should be no test failures when running under Windows NT/2000/XP.
 Many tests I<will> fail under Windows 9x due to the inferior command shell.
 
-The following known test failures under the 64-bit edition of Windows .NET
-Server beta 3 are expected to be fixed before the 5.8.0 release:
-
-    Failed Test              Stat Wstat Total Fail  Failed  List of Failed
-    ------------------------------------------------------------------------
-    ../ext/Encode/t/JP.t        3   768    37    3   8.11%  15 26 37
-    ../ext/Encode/t/perlio.t    7  1792    20    7  35.00%  1-2 5-6 10 14 18
-    ../ext/threads/t/end.t                  6    4  66.67%  3-6
-    op/fork.t                              18    3  16.67%  2 15 17
-
 Some test failures may occur if you use a command shell other than the
 native "cmd.exe", or if you are building from a path that contains
 spaces.  So don't do that.
@@ -284,6 +275,16 @@ contain a header file called "patchlevel.h".  The latest Borland compiler
 option -VI- for backward (bugward) compatibility for using the old Borland
 search algorithm  to locate header files.
 
+If you run the tests on a FAT partition, you may see some failures for
+C<link()> related tests (I<op/write.t>, I<op/stat.t> ...). Testing on
+NTFS avoids these errors.
+
+Furthermore, you should make sure that during C<make test> you do not
+have any GNU tool packages in your path: some toolkits like Unixutils
+include some tools (C<type> for instance) which override the Windows
+ones and makes tests fail. Remove them from your path while testing to
+avoid these errors.
+
 Please report any other failures as described under L<BUGS AND CAVEATS>.
 
 =head2 Installation of Perl on Win32
@@ -613,7 +614,7 @@ Embedding Perl inside a 64-bit application.
 
 =back
 
-=item Running Perl Scripts
+=head2 Running Perl Scripts
 
 Perl scripts on UNIX use the "#!" (a.k.a "shebang") line to
 indicate to the OS that it should execute the file using perl.
@@ -681,8 +682,6 @@ Here's a diversion:  copy "runperl.bat" to "runperl", and type
 "runperl".  Explain the observed behavior, or lack thereof. :)
 Hint: .gnidnats llits er'uoy fi ,"lrepnur" eteled :tniH
 
-=back
-
 =item Miscellaneous Things
 
 A full set of HTML documentation is installed, so you should be