http://qs1969.pair.com?node_id=217531


in reply to ActiveState's PerlApp is causing an odd problem with IO:Socket

It sounds like the module isn't included, and hence isn't used properly at app runtime. It's probably dynamically loaded in a way that PerlApp has problems detecting when deciding which modules to bring along at build time.

The canonical way to solve that problem is to explicitly "use" the module somewhere in your script (preferrably with a little note about PerlApp acting up). But from "IO::Select module is being added at compile time" I take it that you already do that.

What if you "add" or "bind" the file manually with a command line option?

perlapp -h for syntax.


/J

Replies are listed 'Best First'.
Re: Re: ActiveState's PerlApp is causing an odd problem with IO:Socket
by lclemmer (Initiate) on Dec 04, 2002 at 23:21 UTC
    Um. I guess I'm not being clear enough. Thanks for the suggestions, but no joy here.

    When I saw the problem the first thing I tried was to put in a "use IO::Select", then a "require IO::Select" to see if that made a difference. It didn't. Importantly in all cases PerlApp is still smart enough to find the dependent module and tell us:

    Adding Module: e:/Perl/lib/IO/Socket.pm Adding Module: e:/Perl/lib/IO/Select.pm

    The problem isn't that the module isn't there, it's that for some reason the standalone exe is having trouble doing the "method call" to that module, but when using regular perl libraries, install environment, whatever it works fine.

    So, any other ideas?