Fetch and install dmake somewhere on your path (follow the instructions
in the README.NOW file).
+There exists a minor coexistence problem with dmake and Borland C++
+compilers. Namely, if a distribution have C files named with a mixed
+case letters, they will be compiled into appropriate .obj-files named
+with all lowercase letters, and every time when dmake will be invoked
+to bring files up to date, it will try to recompile such files again.
+For example, Tk distribution have a lot of such files, resulting in
+multiple recompiling everytime dmake is invoked. To avoid this, you
+may use the script "sncfnmcs.pl" after successful build. It is
+available in the win32 subdirectory.
+
=item Command Shell
Use the default "cmd" shell that comes with NT. Some versions of the
from where Borland chose to install it, into the Windows system directory
(usually somewhere like C:\WINNT\SYSTEM32) and rerun the test.
+If you're using Borland compiler versions 5.2 and below, you're risking
+to face a problem with finding incorrect header files. Don't be surprised
+when during compiling perl extension "Tk" you will fail because both perl
+and tk contain a header file with same name - "patchlevel.h". The latest
+Borland compilers are free of this misbehaviour, and they even invented
+option -VI- for backward (bugward) compatibility as "Use old Borland
+search algorithm to locate header files".
+
Please report any other failures as described under L<BUGS AND CAVEATS>.
=head2 Installation
=head1 BUGS AND CAVEATS
+Norton AntiVirus interferes with the build process, particularly if
+set to "AutoProtect, All Files, when Opened". Unlike large applications
+the perl build process opens and modifies a lot of files. Having the
+the AntiVirus scan each and every one slows build the process significantly.
+Worse, with PERLIO=stdio the build process fails with peculiar messages
+as the virus checker interacts badly with miniperl.exe writing configure
+files (it seems to either catch file part written and treat it as suspicious,
+or virus checker may have it "locked" in a way which inhibits miniperl
+updating it). The build does complete with
+
+ set PERLIO=perlio
+
+but that may be just luck. Other AntiVirus software may have similar issues.
+
Some of the built-in functions do not act exactly as documented in
L<perlfunc>, and a few are not implemented at all. To avoid
surprises, particularly if you have had prior exposure to Perl
=item Gurusamy Sarathy E<lt>gsar@activestate.comE<gt>
-=item Nick Ing-Simmons E<lt>nick@ni-s.u-net.comE<gt>
+=item Nick Ing-Simmons E<lt>nick@ing-simmons.netE<gt>
=back
Win9x support was added in 5.6 (Benjamin Stuhl).
-Last updated: 22 March 2000
+Last updated: 22 November 2000
=cut