Re^4: Experimenting Ajax - problem installing Apache2::Ajax

[Anonymous Monk]

/etc/init.d/apache2 basically just calls apache2ctl which is in /usr/sbin/apache2ctl which contains

# the path to your httpd binary, including options if necessary
HTTPD='/usr/sbin/apache2'
#

so I've found https
which apxs -> no results
which apxs2 -> no results
Moreover trying to install Apache2::Ajax from source or from cpan doesn't ask me any more to introduce the full path to httpd executable. Maybe the wrong path has been saved somewhere but how to find it?

Summing up:
1) now I know which is the path to httpd but not where are my apxs|apxs2.
2) The dialogue configuration doesn't appear any more.

Here is the output of my Apache2::Ajax installation

 CPAN.pm: Going to build R/RK/RKOBES/Apache2-Ajax-0.1.tar.gz

[   info] generating script t/TEST
Checking if your kit is complete...
Looks good
Writing Makefile for Apache2::Ajax
cp lib/Apache2/Ajax.pm blib/lib/Apache2/Ajax.pm
Manifying blib/man3/Apache2::Ajax.3pm
  /usr/bin/make  -- OK
Running make test
/usr/bin/perl -Iblib/arch -Iblib/lib \
        t/TEST  -clean
[warning] setting ulimit to allow core files
ulimit -c unlimited; /usr/bin/perl /home/om/.cpan/build/Apache2-Ajax-0
+.1/t/TEST -clean
APACHE_TEST_GROUP= APACHE_TEST_HTTPD= APACHE_TEST_PORT= APACHE_TEST_US
+ER= APACHE_TEST_APXS= \
        /usr/bin/perl -Iblib/arch -Iblib/lib \
        t/TEST  -bugreport -verbose=0 
[warning] setting ulimit to allow core files
ulimit -c unlimited; /usr/bin/perl /home/om/.cpan/build/Apache2-Ajax-0
+.1/t/TEST -bugreport -verbose=0
Usage: /etc/init.d/apache2 start|stop|restart|reload|force-reload
Usage: /etc/init.d/apache2 start|stop|restart|reload|force-reload
Usage: /etc/init.d/apache2 start|stop|restart|reload|force-reload
[  error] You are using mod_perl response handlers 
[  error] but do not have a mod_perl capable Apache.
make: *** [run_tests] Error 1
  /usr/bin/make test -- NOT OK
Running make install
  make test had returned bad status, won't install without force

[randyk]

Theoretically, you don't need apxs to run the tests. What might be an idea is to run the tests manually, using the option in Apache::Test to override the runtime configuration, so that you can make sure that the location of httpd you're using is the right one.