in reply to A permanent fix for the Windows 'manifest' issue?

The latest (at this time) release of ExtUtils::MakeMaker, v6.50, claims in its Changes that some provision was made to address the generation of manifest files for DLLs. I'm not sure whether using the latest version addresses the problem, but if so, listing ExtUtils::MakeMaker 6.50 as a prerequisite to your module (in Makefile.PL) should make the issue go away.

Replies are listed 'Best First'.
Re^2: A permanent fix for the Windows 'manifest' issue?
by BrowserUk (Patriarch) on Mar 23, 2009 at 16:05 UTC

    Hm. Attempting CPAN install ExtUtils::MakeMaker sees it pulling and installing v6.48. Which is up from the v6.42_01 that I had, but...it still fails to build XS modules in the same way, for the same reason.

    So I tried:

    cpan> install ExtUtils-MakeMaker-6.50 Warning: Cannot install ExtUtils-MakeMaker-6.50, don't know what it is +. Try the command i /ExtUtils-MakeMaker-6.50/ to find objects with matching identifiers.

    Is there a special incantation to force CPAN to fetch the latest greatest version?


    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.

      It was uploaded yesterday and hasn't replicated to your CPAN mirror yet.

      Or maybe you're using a cached module listing. Try reload index

      Or you could try adding mirror ftp://mirror.csclub.uwaterloo.ca/pub/CPAN/. It has it.

      You can always download the archive and installing it without using cpan.

      perl Makefile.PL nmake nmake test nmake install

      (s/nmake/dmake/ for Strawberry Perl?)

        I'd already tried downloading and installing v6.50 manually but even after a "successful" nmake install, Perl was still finding v6.48.

        Apparently, doing a manual install puts it into perl/lib whereas CPAN puts it into perl/site/lib (or maybe vice versa). So I had to blow away the installed dirs in both paths and redo the manual install to get it to take.

        Once done, it definitely improves things, though there is still one R6034 runtime error during the testing (of mod://PDL] which I will attempt to track down). That required a force install to get PDL installed, but it mostly seems to work.


        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.