My computer's being nice, its giving me a choice of errors (from apache's error_log):
-- 1 -- [Tue May 28 12:12:37 2002] [warn] [client 127.0.0.1] [AxKit] XSP Compilation finished [Tue May 28 12:12:37 2002] [warn] [client 127.0.0.1] [AxKit] Turning off cache! [Tue May 28 12:12:37 2002] [warn] [client 127.0.0.1] [AxKit] Cache: key = d0a18bf86d6212273311e02a7e55bd8a [Tue May 28 12:12:37 2002] [warn] [client 127.0.0.1] [AxKit] Can't create cache directory '/opt/apache/htdocs/test/.xmlstyle_cache': Permission denied [Tue May 28 12:12:37 2002] [warn] [client 127.0.0.1] [AxKit] Can't create cache directory '/opt/apache/htdocs/test/.xmlstyle_cache/d0': No such file or directory [Tue May 28 12:12:37 2002] [warn] [client 127.0.0.1] [AxKit] Can't create cache directory '/opt/apache/htdocs/test/.xmlstyle_cache/d0/a1': No such file or directory [Tue May 28 12:12:37 2002] [notice] child pid 28461 exit signal Segmentation fault (11) -- 2 -- [Tue May 28 12:13:14 2002] [notice] SIGHUP received. Attempting to restart [Tue May 28 12:13:14 2002] [notice] Apache/1.3.24 (Unix) AxKit/1.52 mod_perl/1.26 configured -- resuming normal operations [Tue May 28 12:13:14 2002] [notice] Accept mutex: sysvsem (Default: sysvsem) [Tue May 28 12:13:18 2002] [warn] [client 127.0.0.1] [AxKit] fast handler called for /test/test.xml [Tue May 28 12:13:18 2002] [error] Can't locate object method "new_content_provider" via package "Apache::AxKit::Provider" (perhaps you forgot to load "Apache::AxKit::Provider"?) at /usr/lib/perl5/site_perl/5.6.1/i586-linux/AxKit.pm line 169. The first is generated while running AxKit-1.5.2. The second is generated when trying to run from the current CVS state. Using cpan, I've reinstalled 1.5.2 so I can toggle between the states at will, though I make headway with neither. When tracking 1, I can run through XSLTs, but XSPs of even the simplest nature fail. So, knowing there's been some discussion of this, I moved on to the current CVS version. When tracking 2, ./Apache/AxKit/Provider.pm has the sub new_content_provider clearly defined, and AxKit.pm clearly has 'use Apache::AxKit::Provider' at the top. I'm more concerned with resolving problem 2. If anyone wants to work on 1, I can provide backtraces and more specific hardware details.
