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:
The MinGW64 compiler is available at L<http://sourceforge.net/projects/mingw-w64>.
The latter is actually a cross-compiler targeting Win64. There's also a trimmed
down compiler (no java, or gfortran) suitable for building perl available at:
-L<http://strawberryperl.com/package/kmx/64_gcctoolchain/mingw64-w64-20100123-kmx-v2.zip>
+L<http://strawberryperl.com/package/kmx/64_gcctoolchain/>
NOTE: If you're using a 32-bit compiler to build perl on a 64-bit Windows
operating system, then you should set the WIN64 environment variable to "undef".
than the one being tested.
You will have to make sure that CCTYPE is set correctly and that
-CCHOME points to wherever you installed your compiler. If building with
-gcc-4.x.x, you'll also need to uncomment the assignment to GCC_4XX and
-uncomment the assignment to the appropriate GCCHELPERDLL in the makefile.mk.
+CCHOME points to wherever you installed your compiler.
If building with the cross-compiler provided by
mingw-w64.sourceforge.net you'll need to uncomment the line that sets
Type "dmake" (or "nmake" if you are using that make).
This should build everything. Specifically, it will create perl.exe,
-perl513.dll at the perl toplevel, and various other extension dll's
+perl515.dll at the perl toplevel, and various other extension dll's
under the lib\auto directory. If the build fails for any reason, make
sure you have done the previous steps correctly.
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.