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!

it is intriguing that you are not having the same problem with exetype.pl

Yes - 2 things come to mind. One is that we're possibly using different versions of nmake.exe (mine is "Version 7.00.8882"). The other is that we're probably specifying different values for "CCTYPE" in win32/Makefile. I've stuck with the default "MSVC60" - which seems to be working well enough, though seems a bit of an odd choice. (In that my compiler uses the msvcrt.dll runtime (afaik) it can also be argued that's a very sane choice.)

In any case, I've just reset CCTYPE to MSVC80, and perl still builds ok for me. What setting for CCTYPE have you been using ?

I still haven't got around to trying those amendments you posted ... and it's getting late again ... have to put that off until tomorrow.

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 15, 2010 at 14:29 UTC
    different versions of nmake.exe

    I can't quite see how the version of nmake would affect this. The problem is very definitely a Perl internal error in miniperl.exe.

    I use CCTYPE        = MSVC90FREE as seems to best fit the compiler I'm using.


    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.
      I use CCTYPE = MSVC90FREE

      That would be version 15.something-or-other. I can actually use that, too - it doesn't seem to make much difference.

      I don't get any -Wp64 deprecation warnings, so I've left that flag in. I guess it must still be relevant to my compiler. Ideally, the Makefile would be tweaked so that the flag is omitted for compilers such as yours.

      Your suggested change of $(MINIPERL) to $(PERLEXE) does, of course, work fine for me. Maybe submit a perlbug report about this, along with your suggested fix.

      Still no closer to understanding why your compiler builds a troublesome miniperl.

      Cheers,
      Rob
        That would be version 15.something-or-other.

        Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86

        Ideally, the Makefile would be tweaked so that the flag is omitted for compilers such as yours.

        The mod I posted already did that.

        Still no closer to understanding why your compiler builds a troublesome miniperl..

        I'm not sure if you saw it, but I got this far. But once I realised that I had the newly built full perl executable available for modifying wperl.exe, and that worked, I didn't look any further for the miniperl.exe problem.

        I'll try and work up a Makefile patch later.


        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.