Upgraded to 5.2.0.520 which allows me to compile successfully. However,
when I run this using MS personal web server it crashes the webserver.
When run on Apache, the application seems to hang -- keeps running but
does not display output. Sounds like progress...
Graham Barr wrote:
On 6 Oct 2003, at 23:36, Bruce Bahlmann wrote:
ActiveState
perlapp.exe
Version 5.0.3.503
On http://aspn.activestate.com/ASPN/docs/PDK/Release.html is says that
the latest release is 5.2.0.520 and in its release notes it has
"The DATA filehandle is now supported."
Graham.
note, that I've run this with many other perl scripts including SNMP,
DBI, etc. and it has run flawless. This LDAP module is the first
exception I've seen.
Graham Barr wrote:
On 6 Oct 2003, at 19:39, Chris Ridd wrote:
On 5/10/03 3:27 pm, Bruce Bahlmann <[EMAIL PROTECTED]>
wrote:
When using this module as part of a CGI script and then compiling
using
active state, I receive the following errors (not if I do not compile
and merely run as a plain old perl script, everything works fine).
This
is actually the first time I've had trouble using the activestate
perl
compiler with anything...
seek() on unopened filehandle DATA at
/PerlApp/Net/LDAP/Constant.pm line 33.
readline() on unopened filehandle DATA at
/PerlApp/Net/LDAP/Constant.pm line
36.
"LDAP_SUCCESS" is not exported by the Net::LDAP::Constant module at
/PerlApp/Net/LDAP/Message.pm line 8
I think the DATA filehandle is the magic perl way to access the
non-perl
trailing part of the perl module (I can't find the doc describing this
though) and Constant.pm uses this to work out the codes for each
constant.
Yes it is.
And it sounds like Bruse is using perl2exe, or something similar, to
create a single executable file.
Well unfortunately there are things that I belive do not work with
perl2exe and this is one of them
Graham.
