Changes for make 3.75.1

1 files changed, 19 insertions, 12 deletions

diff --git a/README.W32 b/README.W32
index 80974cb..0104d55 100644
--- a/README.W32
+++ b/README.W32
@@ -1,10 +1,10 @@
-Port of GNU make to Windows NT and Windows 95 
+Port of GNU make to Windows NT and Windows 95
 Builds natively with MSVC 2.x or MSVC 4.x compilers.
 
 To build with nmake on Windows NT or Windows 95:
 
 	1. Make sure cl.exe is in your %Path%. Example:
-	
+
 		set Path=%Path%;c:/msdev/bin
 
 	2. Make sure %include% is set to msvc include directory. Example:
@@ -19,7 +19,7 @@ To build with nmake on Windows NT or Windows 95:
 
 
 There is a bat file (build_w32.bat) for folks who have fear of nmake.
-	
+
 Outputs:
 
 	WinDebug/make.exe
@@ -34,13 +34,13 @@ GNU make and sh.exe:
 	system. If you don't have sh.exe, port falls back to
 	MSDOS mode for launching programs (via a batch file).
 	The MSDOS mode style execution has not been tested too
-	carefully though (I use GNU bash as sh.exe). 
+	carefully though (I use GNU bash as sh.exe).
 
 	There are very few true ports of Bourne shell for NT right now.
-	There is a version of GNU bash available from Cygnus gnu-win32 
-	porting effort.  Other possibilites are to get the MKS version 
-	of sh.exe or to build your own with a package like 
-	NutCracker (DataFocus) or Portage (Consensys). 
+	There is a version of GNU bash available from Cygnus gnu-win32
+	porting effort.  Other possibilites are to get the MKS version
+	of sh.exe or to build your own with a package like
+	NutCracker (DataFocus) or Portage (Consensys).
 
 	Tivoli uses a homegrown port of GNU bash which is not (yet)
 	freely available. It may be available someday, but I am not in control
@@ -58,12 +58,12 @@ Building GNU make on Windows NT and Windows 95 with Microsoft Visual C
 	I did not provide a Visual C project file with this port as
 	the project file would not be considered freely distributable
 	(or so I think). It is easy enough to create one though if
-	you know how to use Visual C. 
+	you know how to use Visual C.
 
 	I build the program statically to avoid problems locating DLL's
 	on machines that may not have MSVC runtime installed. If you
 	prefer, you can change make to build with shared libraries by
-	changing /MT to /MD in the NMakefile (or build_w32.bat). 
+	changing /MT to /MD in the NMakefile (or build_w32.bat).
 
 	Program has not been built under non-Intel architectures (yet).
 
@@ -71,7 +71,7 @@ Building GNU make on Windows NT and Windows 95 with Microsoft Visual C
 
 Pathnames and white space:
 
-	Unlike Unix, WIN32 systems encourage pathnames which
+	Unlike Unix, Windows 95/NT systems encourage pathnames which
 	contain white space (e.g. C:\Program Files\). These sorts of pathnames
 	are legal under Unix too, but are never encouraged. There is
 	at least one place in make (VPATH/vpath handling) where paths
@@ -80,7 +80,7 @@ Pathnames and white space:
 	these sorts of paths could be handled. I offer these suggestions
 	as workarounds:
 
-		1. Use 8.3 notation 
+		1. Use 8.3 notation
 		2. Rename the directory so it does not contain white space.
 
 	If you are unhappy with this choice, this is free software
@@ -105,6 +105,13 @@ SAMBA/NTFS/VFAT:
 	under VFAT. VFAT users may wish to be aware that this port
 	of make does respect case sensitivity.
 
+    Version 3.76 contains some preliminary support for FAT.
+    Make now tries to work around some difficulties with stat'ing of
+    files and caching of filenames and directories internally.
+    There is still a known problem with filenames sometimes being found
+    to have modification dates in the future which cause make to
+    complain about the file and exit (remake.c).
+
 Bug reports:
 
 	Please submit bugs via the normal bug reporting mechanism