in reply to Re^3: Perl 5.12.0 has been released! (exetype problem 64-bit)
in thread Perl 5.12.0 has been released!

With that change, nmake install completes successfully.

Was this an 'nmake install' issue ? I assumed it was happening during 'nmake' and didn't go beyond 'nmake test'.

I'll take a look at the other stuff (and run 'nmake install' if need be) tomorrow .... bedtime over here :-)

Cheers,
Rob
  • Comment on Re^4: Perl 5.12.0 has been released! (exetype problem 64-bit)

Replies are listed 'Best First'.
Re^5: Perl 5.12.0 has been released! (exetype problem 64-bit)
by BrowserUk (Patriarch) on Apr 14, 2010 at 10:04 UTC

    No. It fails with just nmake also.

    I've been using nmake install directly, because if you do nmake, nmake test followed by nmake install, each subsequent pass spends ages re-checking all the /ext /cpan /cpanp etc. directories.

    Doing nmake install saves time, but has no affect on the problem. I don't use the installed builds anyway, so I just put them somewhere out of harms way.


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.