in reply to Re^2: Installing Perl modules on Win64/Perl 5.8
in thread Installing Perl modules on Win64/Perl 5.8

... does this mean I should be installing the Microsoft Windows SDK for Windows 7 instead?

I don't think so. Assuming you're going to be using your compiler with ActivePerl, you (ideally) want the same compiler that built ActivePerl - which is the one that I gave the link to.

My PC is not a server at all, and the operating system is Vista (64 bit), yet that compiler works fine with the w64 builds of ActivePerl.

Cheers,
Rob
  • Comment on Re^3: Installing Perl modules on Win64/Perl 5.8

Replies are listed 'Best First'.
Re^4: Installing Perl modules on Win64/Perl 5.8
by lintunen (Novice) on Mar 25, 2010 at 10:09 UTC
    That link redirects me to install Windows SDK for Windows Server 2008 and .NET Framework 3.5 - do you believe that this is still OK?
[reply]
      That link redirects me to install Windows SDK for Windows Server 2008 and .NET Framework 3.5

      Bastards !!
      It's not the same compiler as was used to build ActivePerl. I don't think it uses the same runtime (msvcrt.dll) as used by 2003 R2, and that can pose a problem in certain situations. Those situations are not common - but that's no consolation if you're wanting to build one of the modules that *are* affected by this. I think you'll also need to remove 'bufferoverflowu.lib' from the 'libs' and 'perllibs' entries in perl/lib/config_heavy.pl - though that's not such a big deal. If you can track down the one I specified (which, I think, is still available) it would be better. Maybe go to http://www.microsoft.com and try a search there for it.

      But if you can't find the "2003 R2" then go with the one you've been re-directed to. (I think BrowserUk uses that one - with good results. I'll /msg him and ask him to correct me if I'm wrong about that.)

      Another approach would be to install that 2008 version and then use it to build your own perl from source.

      Cheers,
      Rob
[reply]
        But if you can't find the "2003 R2" then go with the one you've been re-directed to. (I think BrowserUk uses that one - with good results.

        Indeed. That is the one I use with (mostly) good results. There have been a couple of XS modules that have presented problems to do with duplicate CRTs. However, I believe that those problems are induced by the Win32 perl makefile which explicitly names msvcrt.lib, instead of allowing it to default to the default CRT for the compiler. If that was removed, the CRT problem might go away.

        Another approach would be to install that 2008 version and then use it to build your own perl from source.

        There are three problems with that.

        1. Building the CPAN distribution of Perl is relatively simple, though you may find that you have to start it twice before it runs to completion.

          But with the CPAN distribution you miss out on a lot of the Win32-specific tools that make AS Perl's so useful.

        2. Finding the full AS sources for a given build isn't always easy.

          They're there somewhere--you always seem to have a link for them--but finding them, by navigating the AS site or googling isn't easy, and they have a tendancy to move around. Almost like AS don't really want you to find them.

        3. The AS sources do not build straight out of the box.

          I have succeeded a couple of times. Once with 5.8.8 32-bit and once with 5.10.0 32-bit. Both times the required changes were hard to find, and different!

          I've never succeeded with 5.10.1 32 or 64-bit. Though I admit I haven't tried too hard. Perhaps that's the point.

        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.
[reply]

In Section Seekers of Perl Wisdom