Re: [EMAIL PROTECTED] apxs vs. configure to add modules

2006-05-19 Thread Richard de Vries
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: Is

RE: [EMAIL PROTECTED] apxs vs. configure to add modules

2006-05-19 Thread Richard de Vries
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_proxy

RE: [EMAIL PROTECTED] apxs vs. configure to add modules

2006-05-19 Thread JP
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 was

RE: [EMAIL PROTECTED] apxs vs. configure to add modules

2006-05-19 Thread ohaya
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 source/modules/proxy apxs -i -a -c *.c Jim JP [EMAIL PROTECTED] wrote: Ok, how about cd $source_dir/modules/proxy $apache-home/bin/apxs -i