Tyler MacDonald <[EMAIL PROTECTED]> wrote:
> > Can you try this on another system? That would tell you whether or not
> > there is truly anything wrong with the code, or if you should be looking
> > at reinstalling this system.
> I'm going to test this extensively this weekend if I get the t
On Tue, 2005-11-01 at 13:36 -0800, Tyler MacDonald wrote:
> Could some bizzarre change in unicode settings be affecting the way
> scripts are being compiled post-startup?
That sounds like a good guess. However, you would expect that sort of
problem to be repeatable and consistent. This see
Tyler MacDonald <[EMAIL PROTECTED]> wrote:
> I'm going to test this extensively this weekend if I get the time,
> including testing it on another system. Unfortuantely the other system is
> also perl 5.6.7, httpd 2.0.55, linux 2.6, so if I get the same problems more
> testing will be neccessa
Perrin Harkins <[EMAIL PROTECTED]> wrote:
> > http://search.cpan.org/~CRAKRJACK/ModPerl-PackageRegistry-0.01/
> See also, Apache::Dispatch. Not ported to mp2 yet, I think.
Nice. :-) Geoffrey is using a slightly different model than me
(having multiple pages inside one class, different
Perrin Harkins <[EMAIL PROTECTED]> wrote:
> That's pretty strange. I've only seen errors like this before once, and
> that was on a Win32 system running ActiveState's PerlEX on IIS. At the
> time, I thought it might be a threading issue. Are you using a threaded
> MPM? I see that your Perl was
On Mon, 2005-10-31 at 12:01 -0800, Tyler MacDonald wrote:
> The problem is with compiling code after the apache server has
> already started (ModPerl::Registry, maybe eval qq{} as well, not sure); if I
> compile everything during the startup phase, everything's happy.
That's pretty strange.
On Mon, 2005-10-31 at 11:57 -0800, Tyler MacDonald wrote:
> What a fun problem to solve. Instead of banging my head against the
> wall trying to get things to compile at runtime, I stopped using
> ModPerl::Registry entirely and switched to defining my own pacakges with
> handlers. Problem sol
Perrin Harkins <[EMAIL PROTECTED]> wrote:
> Well, we know there's nothing wrong with HTTP::Request on CPAN, so
> either you have a messed up copy of it there (no idea why this would
> happen), or something is wrong with your system at a pretty low level.
> Possible problems include compiling mod_pe
What a fun problem to solve. Instead of banging my head against the
wall trying to get things to compile at runtime, I stopped using
ModPerl::Registry entirely and switched to defining my own pacakges with
handlers. Problem solved. Of course, how do I map these things to URLs now?
I ended u
On Thu, 2005-10-27 at 15:10 -0700, Tyler MacDonald wrote:
> Today, I'm getting registry errors on my friend's virtual host using
> ModPerl::Registry on mod_perl 2.0.2:
>
> [Thu Oct 27 14:59:44 2005] [error] Global symbol "$class" requires explicit
> package name at /usr/share/perl5/HTTP/Request.pm
On Thu, 27 Oct 2005, Tyler MacDonald wrote:
-8<-- Start Bug Report 8<--
1. Problem Description:
Today, I'm getting registry errors on my friend's virtual host using
ModPerl::Registry on mod_perl 2.0.2:
[Thu Oct 27 14:59:44 2005] [error] Global symbol "$c
11 matches
Mail list logo
