More admonishment that one shouldn't waste one's efforts

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

diff --git a/README.win32 b/README.win32
index 4446600..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 *
 
@@ -274,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
@@ -603,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.