in reply to "dmake: Error code 12" with Crypt::Blowfish and Crypt::DES installation

You have shown us what you get with ActivePerl. When I build Crypt-Blowfish-2.10 on ActivePerl build 817, using dmake 4.7, I find no problem. However, you're output of 'dmake' differs slightly from mine. Whereas you get:
Running Mkbootstrap for Crypt::Blowfish () C:\Perl\bin\perl.exe -MExtUtils::Command -e chmod 644 Blowfish.bs dlltool --def Blowfish.def --output-exp dll.exp
I get:
Running Mkbootstrap for Crypt::Blowfish () C:\Perl\bin\perl.exe -MExtUtils::Command -e chmod 644 Blowfish.bs C:\Perl\bin\perl.exe -MExtUtils::Mksymlists \ -e "Mksymlists('NAME'=>\"Template::Stash::XS\", 'DLBASE' => 'XS', + 'DL_FUNCS' => { }, 'FUNCLIST' => [], 'IMPORTS' = > { }, 'DL_VARS' => []);" dlltool --def Blowfish.def --output-exp dll.exp
You'll note that the 'perl.exe -MExtUtils::Mksymlists....' command is missing in your output.

As a first guess, try updating ExtUtils::MakeMaker to version 6.31, and see if that fixes the problem.

Cheers,
Rob

Replies are listed 'Best First'.
Re^2: "dmake: Error code 12" with Crypt::Blowfish and Crypt::DES installation
by mtar (Novice) on Mar 19, 2007 at 10:16 UTC
    I installed the ExtUtils::MakeMaker to version 6.32 but the problem was not fix.
    Then I checked the Path environment variable in XP.
    There was either C:\Perl\site\bin; and either C:\strawberry-perl\perl\bin...
    The problem was there ;-).
    Now I installed only Vanilla and it's working very well. But in the future I would to resolve this problem with ActiveSate (I like that package). I'll try again on other PC. Thank you for your assistance!
      There was either C:\Perl\site\bin; and either C:\strawberry-perl\perl\bin...
      The problem was there ;-).
      Now I installed only Vanilla and it's working very well


      Were you able to determine exactly what the problem was ?
      It's not of monumental importance, but it puzzles me nonetheless. I have both ActivePerl and Strawberry Perl on the same box, and I cannot reproduce the problem you reported. Even when both ActivePerl and Strawberry Perl are in the 'path' (which is something I don't usually allow), there's still no problem for me.

      Strawberry Perl typically sets INCLUDE and LIB environment variables. I also couldn't find any problem with that - though, afaict, there's no point in setting those environment variables. (I don't know why Strawberry Perl does that.)

      It would be interesting to see what running 'set' produced when the failure was occurring. (Perhaps it's now too late :-)

      Cheers,
      Rob