apxs crashing my installation of PHP as a loadable module

Yow, I cannot get PHP4 built as a loadable module on my Linux dedicated server. I compile Apache (1.3.12), I see the binary file apxs in the /usr/local/apache/bin directory, then I run the following commands to build PHP:

./configure
--with-apxs=/usr/local/apache/bin/apxs
--with-config-file-path=/usr/local/apache
--with-mysql=/usr/local/mysql
--with-xml
--enable-track-vars
--enable-magic-quotes
--enable-debugger
<Enter key>

(from Professional PHP Programming, page 25)

and then this is what I get back:

...
Configuring SAPI modules
checking for AOLserver support... no
checking for Apache module support via DSO through APXS...
Usage: apxs -g [-S <var>=<val>] -n <modname>
apxs -q [-S <var>=<val>] <query> ...
apxs -c [-S <var>=<val>] [-o <dsofile>] [-D <name>[=<value>]]
[-I <incdir>] [-L <libdir>] [-l <libname>] [-Wc,<flags>]
[-Wl,<flags>] <files> ...
apxs -i [-S <var>=<val>] [-a] [-A] [-n <modname>] <dsofile> ...
apxs -e [-S <var>=<val>] [-a] [-A] [-n <modname>] <dsofile> ...
configure: error: Sorry, I cannot run apxs. Either you need to install Perl or you need to pass the absolute path of apxs by using --with-apxs=/absolute/path/to/apxs

--------------

Perl is installed and works just fine, thank you. apxs is right where it 'spoda be, with the absolute path being used.

Can anybody think what might be the trouble here?

The configure script seems to be getting the same results that one gets when manually running apxs.pl with no parameters-- it just spits out the usage instructions, which is crashing the configure script.

THANKS ...

Dave Baker

How did you install apache? What configure options?

I, er, uh, didn't include mod.so when I compiled Apache ...

Fixed 'er right up.

Thanks!

(To find out whether mod.so has been compiled into Apache -- this module is necessary in order to use dynamically-loaded modules -- use the "-l" option when calling the Apache binary (httpd) from a command line:

/path/to/apache_binary/httpd -l

This will produce a list all modules that have been compiled into your Apache binary; mod.so oughta be included. If not, recompile Apache with mod.so included.)

[This message has been edited by DaveBaker (edited October 06, 2000).]

<BLOCKQUOTE><font size="1" face="Verdana,Arial,Helvetica">quote:</font><HR>Originally posted by DaveBaker:
I, er, uh, didn't include mod.so when I compiled Apache ...

Fixed 'er right up.

Thanks!

(To find out whether mod.so has been compiled into Apache -- this module is necessary in order to use dynamically-loaded modules -- use the "-l" option when calling the Apache binary (httpd) from a command line:

/path/to/apache_binary/httpd -l

This will produce a list all modules that have been compiled into your Apache binary; mod.so oughta be included. If not, recompile Apache with mod.so included.)

[This message has been edited by DaveBaker (edited October 06, 2000).][/quote]

<BLOCKQUOTE><font size="1" face="Verdana,Arial,Helvetica">quote:</font><HR>Originally posted by DaveBaker:
I, er, uh, didn't include mod.so when I compiled Apache ...

Fixed 'er right up.

Thanks!

(To find out whether mod.so has been compiled into Apache -- this module is necessary in order to use dynamically-loaded modules -- use the "-l" option when calling the Apache binary (httpd) from a command line:

/path/to/apache_binary/httpd -l

This will produce a list all modules that have been compiled into your Apache binary; mod.so oughta be included. If not, recompile Apache with mod.so included.)

[This message has been edited by DaveBaker (edited October 06, 2000).][/quote]

I did this, also included path to apxs, reinstalled perl5 (latest), included the dynamic build manually with --enable-rule=SHARED_CORE, have mod.so.c and http_core.c in my httpd -l report. So, why does it still give me the exact same message as above? Any help would be appreciated....I've done this about 10 times and this is the first time I've never been able to work through it.