in reply to Problems creating Crypt::OpenPGP standalone exe

boat73, I'm not sure about the others, but I've seen that ActiveState has stated that Crypt::OpenPGP fails all tests. From what I can tell though, it's because the test suite didn't bother to create the basic key files and location files. This might be why perlapp won't work.

Since you're doing this on Windows, which version of Perl are you using (ActiveState or cygwin and which build)? If you try to run the executable from the same directory as where the script version works, does it work there? Have you tried inserting some debugging print statements between each step of your program to see where the compiled version hangs? My guess is that the compiled version can't find some file which the scripted version can. . .

- - arden.

  • Comment on Re: Problems creating Crypt::OpenPGP standalone exe

Replies are listed 'Best First'.
Re: Re: Problems creating Crypt::OpenPGP standalone exe
by PodMaster (Abbot) on Mar 22, 2004 at 09:17 UTC
    I've seen that ActiveState has stated that Crypt::OpenPGP fails all tests. From what I can tell though, it's because the test suite didn't bother to create the basic key files and location files.
    I wouldn't rely on ActiveState's automated ppm buildstatus. All tests pass for me.
    Read more... (404 Bytes)
    Since you're doing this on Windows, which version of Perl are you using (ActiveState or cygwin and which build)?
    cygwin runs on windows but cygwin is not windows. When somebody says they're running perl on windows cygwin is not involved (its probably activeperl or at least activeperl flavored perl, never cygwin).

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]

In Section Seekers of Perl Wisdom