[mp1] Apache/mod_perl startup problems - PL_nowarn

2004-04-07 Thread William McKee
Hi List, I've spent the last several hours trying to figure out the following error message that I receive with Apache 1.3.29 and mod_perl 1.29: /usr/local/apache/bin/httpd: relocation error: /usr/local/apache/bin/httpd: undefined symbol: PL_dowarn bin/apachectl start: htt

Re: [mp1] Apache/mod_perl startup problems - PL_nowarn

2004-04-07 Thread Stas Bekman
William McKee wrote: Hi List, I've spent the last several hours trying to figure out the following error message that I receive with Apache 1.3.29 and mod_perl 1.29: /usr/local/apache/bin/httpd: relocation error: /usr/local/apache/bin/httpd: undefined symbol: PL_dowarn bin/

Re: [mp1] Apache/mod_perl startup problems - PL_nowarn

2004-04-07 Thread William McKee
On Wed, Apr 07, 2004 at 12:39:33AM -0700, Stas Bekman wrote: > William, why do you check a binary, which is not the one that you get > the error from? You need to check /usr/local/apache/bin/httpd instead. > (of course it could be the same binary, but still...) Because I thought it was the same

Re: [mp1] Apache/mod_perl startup problems - PL_nowarn

2004-04-07 Thread Stas Bekman
William McKee wrote: On Wed, Apr 07, 2004 at 12:39:33AM -0700, Stas Bekman wrote: William, why do you check a binary, which is not the one that you get the error from? You need to check /usr/local/apache/bin/httpd instead. (of course it could be the same binary, but still...) Because I thought

Re: [mp1] Apache/mod_perl startup problems - PL_nowarn

2004-04-07 Thread William McKee
On Wed, Apr 07, 2004 at 10:37:15AM -0700, Stas Bekman wrote: > And that's your problem. It picks the wrong perl library. Move it somewhere > out of /usr/lib and rebuild again, and it'll probably be fine. What is that > libperl.so? I didn't consider that route. > Your real libperl.so if any tha

Re: [mp1] Apache/mod_perl startup problems - PL_nowarn

2004-04-07 Thread Stas Bekman
William McKee wrote: Having libperl.so in /usr/lib/ is a great reason for lots of obscure problems, when you have one more perl installed elsewhere. That's why perl puts its libperl.so under its private tree. But some distros play it smart... Yep that was the root of the problem. Apparently D