Hi,
This was with an older version of Apache (2.0.52), but I just did this this
week to compile the mod_proxy modules on Solaris:
cd /modules/proxy
apxs -i -a -c *.c
Jim
JP <[EMAIL PROTECTED]> wrote:
> >
> > Ok, how about
> >
> > cd $source_dir/modules/proxy
> > $apache-home/bin/apxs
>
> Ok, how about
>
> cd $source_dir/modules/proxy
> $apache-home/bin/apxs -i -a -c *proxy*.c
>
That compiles, but produces the symbol resolution error at runtime. I was
wondering if I am missing something obvious. The docs say to use apxs to
compile modules outside of the source tree, so I
Ok, how about
cd $source_dir/modules/proxy
$apache-home/bin/apxs -i -a -c *proxy*.c
I know I got it to work using some sort of wildcards.
I'll try to see if I can find it back in my shell's
history.
--- JP <[EMAIL PROTECTED]> wrote:
>
>
>
>
> >
> > I had a similiar problem with the mod_pr
>
> I had a similiar problem with the mod_proxy modules,
> but even specifiying these modules during the
> "./configure" phase did not work properly for me.
>
> Try this:
>
> cd $source_dir/modules/proxy
> $apache-home/bin/apxs -i -a -c *.c
>
> R.
>
Hey. Here's what I get:
Put a
I had a similiar problem with the mod_proxy modules,
but even specifiying these modules during the
"./configure" phase did not work properly for me.
Try this:
cd $source_dir/modules/proxy
$apache-home/bin/apxs -i -a -c *.c
R.
--- JP <[EMAIL PROTECTED]> wrote:
> Hi. My question is:
> I
Hi. My question is:
Is there a proper method to adding delivered modules to httpd 2.2.2 after
the initial run of configure, make, and install? That is, should I be able
to use apxs to add modules, as DSOs, after the initial build, or should I be
using configure to compile and add them?
I'm using
