You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Sarah <sa...@gmail.com> on 2006/05/18 00:16:55 UTC

Problem Building mod_jk with --with-apxs

Hi,

I was trying to build jakarta-tomcat-connectors-1.2.15 for Apache 1.3.36
and couldn't get configure to use apxs. Here's what I tried:

    $ cd /usr/local/installers/apache_1.3.36
    $ ./configure --prefix=/usr/local
    $ make
    $ sudo make install

Ok, so Apache builds and installs with no problem. Now try jk:

    $ cd /usr/local/installers/jakarta-tomcat-connectors-1.2.15-src
/jk/native
    $ ls -l /usr/local/bin/apxs
    -rwxr-xr-x  1 root root 24318 2006-05-17 13:23 /usr/local/bin/apxs
    $ ./configure --with-apxs=/usr/local/bin/apxs
    ...
    could not find /usr/local/bin/apxs
    configure: error: You must specify a valid --with-apxs path

If *I* can see apxs, why can't configure? I also found a comment
somewhere that said I could just use --with-apxs without specifying
the full path, as long as apxs was on the PATH; that didn't work either.
I did verify that apxs runs, too. And I tried pointing --with-apxs
at the pre-"make install" copy, which it couldn't find either, plus
that copy of apxs points at /usr/local/bin/perl, which is not
installed on my system.

Hmm, ok, how about using mod_jk as a static module instead?

    $ cd /usr/local/installers/jakarta-tomcat-connectors-1.2.15-src
/jk/native
    $./configure --with-apache=/usr/local/installers/apache_1.3.36
    $ make
    $ make install
    $ cd /usr/local/installers/apache_1.3.36
    $ ./config.status --prefix=/usr/local
--activate-module=src/modules/jk/libjk.a
    $ make
    $ sudo make install
    $ /usr/local/bin/httpd -l
    Compiled-in modules:
      http_core.c
      ...
      mod_jk.c

So in the end, I have what I need; for my purposes, static vs. dynamic
really doesn't matter much.

But, um, just out of curiosity, what gives? Why didn't apxs work?
What did I do wrong?

I tried searching some old messages from the list, and found some mentions
of the same problem, but not a clear explanation of what's actually wrong.

The system in question is running Ubuntu 5.10.

Thanks,

Sarah