Hi Neil,
> > I am trying out Embperl 2.0 again. It appears (at first glance) to
> > work with most of existing code, but it will take quite a lot more
> > testing before I commit it to my production box. The big problem so
> > far is the startup.pl file. I preload all the html and epl files to
> > maximize shared memory. This involves traversing the
> directory tree,
> > calling this on each file:
> >
> > Embperl::Execute ({
> > inputfile => $filename,
> > import => 0,
> > path => $path,
> > escmode => 0,
> > options => 16});
> >
> > However this produces the same error for every file:
> >
> > [14953]ERR: 56: : Unknown Provider epcompile
> >
> > Apache does appear to complete starting, but I am not sure
> what state
> > it is in, with these error messages. It seems to imply that
> the code
> > is not being compiled, which obviously would not bode well for it
> > being in shared memory.
Mmmh, this happens when Embperl Perl part is loaded, but the C part not...
> >
> > The documentation for Execute appears to not be present
> under the new
> > 2.0 docs.
See
perldoc Embperl::Config
> Has it changed in some way?
Basicly it is the same, some minor changes, for example options => 16 in now
the default and you would change it with input_escmode
> Am I not supposed to
> be able to
> > preload modules under 2.0 any more, or is this a
> straightforward bug?
> >
> > The system is Debian Sarge (stable), Perl is "5.8.4 built for
> > i386-linux-thread-multi" (the one that comes with Sarge), Embperl
> > 2.0rc4 (i.e. freshly downloaded & built from source, all tests
> > passed), mod_perl 1.29, apache 1.3.33.
>
Is mod_perl staticly compiled into Apache or loaded as module?
> Doing some searching around, I just realized that I asked
> about this way back in 2002:
>
> http://www.gossamer-threads.com/lists/modperl/embperl/15591
>
> I'm not sure why the thread just petered out.
It was a bug back in 2002, but it should be fix for at least a year
>
> I also looked at the $path I am passing in, to make sure it
> makes sense. I was including all the parent directories going
> back up from the file being executed, separated by colons.
> Also a lib directory. I thought maybe it is missing some
> standard path stuff in there, which might be why it's not
> finding epcompile any more, so I added @INC on the end of
> $path, separated by colons. No change.
This has nothing to do with path or @INC, it happen before all this stuff
can work. It's a problem with initialisation of Embperl, which in turn is a
problem with the way the module stuff works under Apache.
> This does work, btw, in Embperl 1.3.
>
Yes, because Embperl 1.3 doesn't knows about Providers :-)
> I am stumped... anybody else tried this? I can't be the only
> one preloading my code for better memory sharing.
>
> I've sent three messages now in a row, and no responses. Have
> I offended the Embperl gods in some way?
>
I am not a god, but at least me you didn't have offended :-)
I didn't answer about the thread question, because I didn't ever saw this,
Embperl itself doesn't uses threads and I don't use Debian, so there simply
nothing I can tell about this, beside the fact that some code seems to start
a thread which isn't finished when the Perl interpreter ends.
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
