Net::POP3->new() fails in PerlApp compiled script

[Eric McDaniel]

This may be a question for ActiveState support, but just in case anyone out
there knows what the problem is...

My call to Net:OP3->new() works fine when run through the perl
interpreter, but fails when I compile the script with PerlApp and run it. My
system is Windows 2000, ActiveState Perl 5.8.0 build 806, PerlApp 5.2.0
build 520.

Here is the script:

##############################################################
#!perl -w

use strict;

use Net:OP3;

my $p = Net:OP3->new('mail.mydomain.com', Debug=>99)
or die('Server connection error');
##############################################################

The command'perl pop3.pl' yields this (successful) output:

Net:OP3: Net:OP3(2.23)
Net:OP3: Net::Cmd(2.21)
Net:OP3: Exporter(5.566)
Net:OP3: IO::Socket::INET(1.26)
Net:OP3: IO::Socket(1.27)
Net:OP3: IO::Handle(1.21)

Net:OP3=GLOB(0x1d524ac)<<< +OK X1 NT-POP3 Server mail013.readyhosting.com
(IMail 7.10 2193398-16)
Net:OP3=GLOB(0x1d524ac)>>> RSET
Net:OP3=GLOB(0x1d524ac)<<< +OK
Net:OP3=GLOB(0x1d524ac)>>> QUIT
Net:OP3=GLOB(0x1d524ac)<<< +OK POP3 Server saying Good-Bye


However, when I compile it with PerlApp ('perlapp pop3.pl') and run the
resulting pop3.exe, it dies:

Server connection error at pop3.pl line 7.


Any ideas?

Thanks.

-Eric

 

[Bart Lateur]

Any ideas?

Your error message isn't that helpful. See if you can print out a string
with some more info. See the docs for Net:OP3 -- I'm a bit lazy
myself.

Anyway, it's rather typical for apps compiled with PerlApp or its
distant nephew perl2exe, if it fails, that one or more modules were
overlooked when building the distribution. (= the EXE). At first look I
see a lot of "use" statements in Net:OP3, so I suggest you try and
dump the contents of %INC before that call on line 3. Data:umper would
be fine. Let's see if one isn't listed that is listed in the list you
gave in your post.

 

[James Willmore]

This may be a question for ActiveState support, but just in case anyone out
there knows what the problem is...

My call to Net:OP3->new() works fine when run through the perl
interpreter, but fails when I compile the script with PerlApp and run it. My
system is Windows 2000, ActiveState Perl 5.8.0 build 806, PerlApp 5.2.0
build 520.

Here is the script:

##############################################################
#!perl -w

use strict;

use Net:OP3;

my $p = Net:OP3->new('mail.mydomain.com', Debug=>99)
or die('Server connection error');
##############################################################

The command'perl pop3.pl' yields this (successful) output:

Net:OP3: Net:OP3(2.23)
Net:OP3: Net::Cmd(2.21)
Net:OP3: Exporter(5.566)
Net:OP3: IO::Socket::INET(1.26)
Net:OP3: IO::Socket(1.27)
Net:OP3: IO::Handle(1.21)

Net:OP3=GLOB(0x1d524ac)<<< +OK X1 NT-POP3 Server mail013.readyhosting.com
(IMail 7.10 2193398-16)
Net:OP3=GLOB(0x1d524ac)>>> RSET
Net:OP3=GLOB(0x1d524ac)<<< +OK
Net:OP3=GLOB(0x1d524ac)>>> QUIT
Net:OP3=GLOB(0x1d524ac)<<< +OK POP3 Server saying Good-Bye


However, when I compile it with PerlApp ('perlapp pop3.pl') and run the
resulting pop3.exe, it dies:

Server connection error at pop3.pl line 7.


Any ideas?

With perlcc, you have to include the modules that you have included in
the script. It may be the same with PerlApp.

Just a thought.

Jim

 

[Eric McDaniel]

Your error message isn't that helpful. See if you can print out a string
with some more info. See the docs for Net:OP3 -- I'm a bit lazy
myself.

Anyway, it's rather typical for apps compiled with PerlApp or its
distant nephew perl2exe, if it fails, that one or more modules were
overlooked when building the distribution. (= the EXE). At first look I
see a lot of "use" statements in Net:OP3, so I suggest you try and
dump the contents of %INC before that call on line 3. Data:umper would
be fine. Let's see if one isn't listed that is listed in the list you
gave in your post.

I would print out a better error message if I knew where to get one. The
Net:OP3 docs say nothing about what happens when the constructor fails.
The observed behaviour is that it returns undef, with no indication of what
the problem was. Even with Debug=>99, I get no debug output when the
constructor fails.

I'll see if I can figure out what are the dependent modules.

-Eric