Re: [us...@httpd] Strange compile error for Apache 2.2.11

2009-04-13 Thread Nishaliny Thurairatnam
Hi again, So I manage to get my Apache installed in the end. For those who'd like to know/looking for a similar solution, all I had to do was: > yum list apr*, [list displayed - My versions were slightly older, and there were some apr-utils that I was missing] > yum install apr* [Installed

Re: [us...@httpd] Strange compile error for Apache 2.2.11

2009-04-12 Thread Nishaliny Thurairatnam
Ok, so I spoke waaay too soon! After a successful configure, I had an epic "make" failure!! Making all in srclib make[1]: Entering directory `/home/foodreg/Installers/httpd-2.2.11/srclib' Making all in pcre make[2]: Entering directory `/home/foodreg/Installers/httpd-2.2.11/srclib/pcre' make[3]:

Re: [us...@httpd] Strange compile error for Apache 2.2.11

2009-04-12 Thread Nishaliny Thurairatnam
Hi Prasanna, Thank you for your reply...I'm definitely no Apache expert, but I think I decided to arrange my configure options this way before, because I'd read(in the Apache documentation...I think) that --enable-modules=all doesn't actually enable all modules, and that's why we have to speci

Re: [us...@httpd] Strange compile error for Apache 2.2.11

2009-04-10 Thread Prasanna Ram Venkatachalam
Also... Why do u need --enable-modules=all and --enable-mods-shared=most?? One will statically compile all into httpd and other will create .so files for most. Based on your requirement i think u can remove one of them. I personally suggest removing first. Just a thought! Regardss Prasanna Ram O

Re: [us...@httpd] Strange compile error for Apache 2.2.11

2009-04-10 Thread Prasanna Ram Venkatachalam
Hmmm.. i am not sure about the second error. But the first one related to apr rings some bell. Did you try using --with-apr option to explicitly mention path to apr libraries if you have them separately built? Prasanna Ram On Fri, Apr 10, 2009 at 10:25 PM, Nishaliny Thurairatnam wrote: > Hi, >