Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

Re: Compile PERL from source on Windows

by syphilis (Chancellor)
on Mar 11, 2013 at 22:37 UTC ( #1022885=note: print w/replies, xml ) Need Help??

in reply to Compile PERL from source on Windows

At what stage of 'nmake test' does the error occur ?
I've just tried out 5.16.2, using MSVC++ 7.1 and couldn't reproduce the error - though the test suite hangs for me at:
../cpan/CPANPLUS/t/19_CPANPLUS-Dist.t ............................. 32 +/?
I build perl from source quite a bit, and the 32-bit builds usually hang at some point during the running of the tests. (This has been going on for so long that I don't care any more - I just install and be done with it.)

From where did you obtain the perl-5.16.2 source ?
In the Makefile, you are expected to specify whether you're using the free version or the full version of 2010. Did you get that part right ? (Even if you didn't, it seems unlikely to me that would cause the error you're seeing.)

Can you google up any fail reports that are similar to yours ?


Replies are listed 'Best First'.
Re^2: Compile PERL from source on Windows
by MGoBlue (Novice) on Mar 21, 2013 at 00:03 UTC
    Thanks for the reply Rob...

    Per previous suggestions, I went and got 5.16.3. Getting the same error but I'm not missing any files. I must have overlooked it previously.

    Yep, I set up the CCTYPE in the makefile correctly.

    I tried Googling before I posted here.

    At any rate, commenting out the test suite is no beuno as it will fail nmake install in the same spot. Both nmake test and nmake install fail in the same spot:

    Can't extract version from pod/perldelta.pod at Porting/ line 117. NMAKE : fatal error U1077: '..\perl.exe' : return code '0xff' Stop.

    If you build from source regularly, do you mind sharing the secret sauce?


      Three things that would make the task easier:

      1) Post the link to the actual source tarball that you downloaded. This will enable me (or anyone else who is interested) to ensure that we have the same source;

      2) Post, on your public scratchpad the contents of the win32/Makefile (after you've edited it). This allows us to see for ourselves that it looks sane;

      3) Post a larger slice (or the entire lot) of the 'nmake test' output (again, on your public scratchpad). I'd like a better idea of precisely when this failure occurs ... and I'd also like to be sure there's nothing relevant in the lead up to the error.
      The error is occurring before *any* tests are run ... right ?

      Hopefully then we can work out what's going wrong.

      With what do you unpack the source ? If it's a GUI app (such as Winzip) try to make sure that it's unpacking the source in "binary" (not "text" or "smart" or somesuch) mode.


        Thanks for the reply... here's the info as requested:


        2) It's on my scratchpad. In the first "section"

        3) It's on my scratchpad. In the second "section"; below the makefile contents. I didn't post the whole thing. Just the leadup to the failure.

        Regarding archiving, I've tried to unpack the source with both WinZip and the unzip I have loaded from cygwin:

        $ unzip -v

        UnZip 6.00 of 20 April 2009, by Cygwin. Original by Info-ZIP.

        Latest sources and executables are at ; see for other sites.

        Compiled with gcc 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) for Unix (Cygwin) on Aug 4 2009.

        UnZip special compilation options: ASM_CRC COPYRIGHT_CLEAN (PKZIP 0.9x unreducing method not supported) SET_DIR_ATTRIB SYMLINKS (symbolic links supported, if RTL and file system permit) TIMESTAMP UNIXBACKUP USE_EF_UT_TIME USE_UNSHRINK (PKZIP/Zip 1.x unshrinking method supported) USE_DEFLATE64 (PKZIP 4.x Deflate64(tm) supported) UNICODE_SUPPORT char coding: UTF-8 (handle UTF-8 paths) MBCS-support (multibyte character support, MB_CUR_MAX = 6) LARGE_FILE_SUPPORT (large files over 2 GiB supported) ZIP64_SUPPORT (archives using Zip64 for large files supported) USE_BZIP2 (PKZIP 4.6+, using bzip2 lib version 1.0.5, 10-Dec-2007) VMS_TEXT_CONV WILD_STOP_AT_DIR decryption, version 2.11 of 05 Jan 2007

        UnZip and ZipInfo environment options: UNZIP: none UNZIPOPT: none ZIPINFO: none ZIPINFOOPT: none

        Both programs used to extract tarball have given me the same results.

        Thanks again for your help!

      If you build from source regularly, do you mind sharing the secret sauce?

      There is no secret sauce.

      Look at Porting/

      Look at pod/perldelta.pod

      Compare what you have to what is online

      my @want = $contents =~ /perldelta - what is new for perl v(5)\.(\d+)\.(\ +d+)\n/; die "Can't extract version from $filename" unless @want;

      perldelta - what is new for perl v5.16.2

      There is no way for that to fail, unless perldelta is empty

      Why is your perldelta empty?

        Hello... thanks for the reply!

        My perldelta.pod is not empty.

        In my either my extracted perldelta.pod and the manifest ( The files are the same. I do not see an entry which says:

        perldelta - what is new for perl v5.16.3

        Rather, that line is found on the description page for that file. and the manifest ( are the same too.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1022885]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (11)
As of 2017-12-13 17:31 GMT
Find Nodes?
    Voting Booth?
    What programming language do you hate the most?

    Results (372 votes). Check out past polls.