No, I just had to track the error (it was happening in URI->implementor when it extracted the protocol string "https" out of the URL and was looking for URI::https. Not finding (in the temp perl2exe directory), it uses URI::_foreign instead and then can't find there method "host". Because it's a run-time thing, perl2exe couldn't have known to include URI::https). Then I just added "use URI::https" to the script. I didn't see anything of that sort (forcing a module on the command line) in the perl2exe doc anyhow, other than passing perl command line options like -M.
On a related note -- getting a stack trace would have saved me a few hours, but my Active State Perl was not compiled with -DDEBUGGING switch, I guess, and refuses option -D. Has anyone recompiled Active Perl with -DDEBUGGING? -----Original Message----- From: Meidling, Keith [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 24, 2002 4:11 AM To: 'Vitaly Kupisk' Subject: RE: perl2exe -- my bad Was there something you had to specify on the command line to get it to work??? -----Original Message----- From: Vitaly Kupisk [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 23, 2002 6:56 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: perl2exe -- my bad Thanks all, I figured it out -- there are 2 https modules, LWP::Protocol::https and URI::https and I wasn't "use"ing the URI one. Vitaly _______________________________________________ ActivePerl mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/activeperl _______________________________________________ ActivePerl mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/activeperl
