following compilers on the Intel x86 architecture:
Borland C++ version 5.02 or later
- Microsoft Visual C++ version 6.0 or later
+ Microsoft Visual C++ version 6.0 or later (*)
Gcc by mingw.org gcc version 3.2 or later
Gcc by mingw-w64.sf.net gcc version 4.4.3 or later
+(*) NOTE: Support for Visual C++ 2010 is not yet complete. This latest
+version of VC++ introduces some new C<errno.h> constants which conflict
+with Perl's current setting of them to match the corresponding WSAE*
+constants' values. Until this issue is resolved you will see several test
+failures (in F<cpan/autodie/t/flock.t>, F<dist/IO/t/io_multihomed.t >,
+F<dist/Net-Ping/t/450_service.t> and F<dist/Net-Ping/t/510_ping_udp.t>)
+and experience other problems in code involving sockets.
+
Note that the last two of these are actually competing projects both
delivering complete gcc toolchain for MS Windows:
=item Command Shell
-Use the default "cmd" shell that comes with NT. Some versions of the
+Use the default "cmd" shell that comes with Windows. Some versions of the
popular 4DOS/NT shell have incompatibilities that may cause you trouble.
If the build fails under that shell, try building again with the cmd
shell.
Makefile if you're using VC++ 6.0 without the latest service pack and
the linker reports an internal error.
-If you have either the source or a library that contains des_fcrypt(),
-enable the appropriate option in the makefile. A ready-to-use version
-of fcrypt.c, based on the version originally written by Eric Young at
-ftp://ftp.funet.fi/pub/crypt/mirrors/dsi/libdes/, is bundled with the
-distribution and CRYPT_SRC is set to use it.
-Alternatively, if you have built a library that contains des_fcrypt(),
-you can set CRYPT_LIB to point to the library name.
-Perl will also build without des_fcrypt(), but the crypt() builtin will
-fail at run time.
-
If you want build some core extensions statically into perl's dll, specify
them in the STATIC_EXT macro.
There should be no test failures.
+(If you're using VC++ 2010 then you will currently see several test failures,
+as noted in the list of supported compilers above.)
+
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.
arising from the inability to find the Borland Runtime DLLs on the system
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.
+(usually somewhere like C:\WINDOWS\SYSTEM32) and rerun the test.
If you're using Borland compiler versions 5.2 and below, you may run into
problems finding the correct header files when building extensions. For
The crucial thing to understand about the Windows environment is that
the command line you type in is processed twice before Perl sees it.
-First, your command shell (usually CMD.EXE on Windows NT, and
-COMMAND.COM on Windows 9x) preprocesses the command line, to handle
-redirection, environment variable expansion, and location of the
-executable to run. Then, the perl executable splits the remaining
-command line into individual arguments, using the C runtime library
-upon which Perl was built.
+First, your command shell (usually CMD.EXE) preprocesses the command
+line, to handle redirection, environment variable expansion, and
+location of the executable to run. Then, the perl executable splits
+the remaining command line into individual arguments, using the
+C runtime library upon which Perl was built.
It is particularly important to note that neither the shell nor the C
runtime do any wildcard expansions of command-line arguments (so
character is the double quote ("). It can be used to protect spaces
and other special characters in arguments.
-The Windows NT documentation has almost no description of how the
+The Windows documentation has almost no description of how the
quoting rules are implemented, but here are some general observations
based on experiments: The C runtime breaks arguments at spaces and
passes them to programs in argc/argv. Double quotes can be used to
is left as an exercise to the reader :)
One particularly pernicious problem with the 4NT command shell for
-Windows NT is that it (nearly) always treats a % character as indicating
+Windows is that it (nearly) always treats a % character as indicating
that environment variable expansion is needed. Under this shell, it is
therefore important to always double any % characters which you want
Perl to see (for example, for hash variables), even when they are
=item 1
-There is a facility called "file extension associations" that will
-work in Windows NT 4.0. This can be manipulated via the two
-commands "assoc" and "ftype" that come standard with Windows NT
-4.0. Type "ftype /?" for a complete example of how to set this
-up for perl scripts (Say what? You thought Windows NT wasn't
-perl-ready? :).
+There is a facility called "file extension associations". This can be
+manipulated via the two commands "assoc" and "ftype" that come
+standard with Windows. Type "ftype /?" for a complete example of how
+to set this up for perl scripts (Say what? You thought Windows
+wasn't perl-ready? :).
=item 2
Most C<socket()> related calls are supported, but they may not
behave as on Unix platforms. See L<perlport> for the full list.
-Perl requires Winsock2 to be installed on the system. If you're
-running Win95, you can download Winsock upgrade from here:
-
-http://www.microsoft.com/windows95/downloads/contents/WUAdminTools/S_WUNetworkingTools/W95Sockets2/Default.asp
-
-Later OS versions already include Winsock2 support.
Signal handling may not behave as on Unix platforms (where it
doesn't exactly "behave", either :). For instance, calling C<die()>
https://perl5.git.perl.org / perl5.git / blobdiff