RE: Compiled-in but not recognized
Just to update that I thankfully have this working now :) It was a corrupted mod_perl.c file from the source tree that was causing the issue. Thanks. Hi there, On Sun, 11 Aug 2002, Colin wrote: I know this is a recurring problem but bear with me ... :) httpd -l Compiled-in modules: http_core.c mod_so.c mod_perl.c pwd? I think that Ged was suggesting you might have multiple httpd binaries on your system, and was suggesting that you verify you're running the binary you think you're running. It's really annoying when you're trying to debug a program, and the program you're running is not the one you're adding the debugging statements to. However, I suspect most of us have done it on occasion. Ed How the #*! is it getting past all those debug statements without hitting any?!?! - Me
Re: Compiled-in but not recognized
Hi there, On Sun, 11 Aug 2002, Colin wrote: I know this is a recurring problem but bear with me ... :) httpd -l Compiled-in modules: http_core.c mod_so.c mod_perl.c pwd? Syntax error on line 1141 of /usr/local/apache/conf/httpd.conf: Invalid command 'PerlHandler', perhaps mis-spelled or defined by a module not included in the server configuration [snip] Any adivce on this Tell us which of the httpd binaries on your system you're running 73, Ged.
RE: Compiled-in but not recognized
-Original Message- From: Ged Haywood [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 11, 2002 6:02 PM Subject: Re: Compiled-in but not recognized Hi there, On Sun, 11 Aug 2002, Colin wrote: I know this is a recurring problem but bear with me ... :) httpd -l Compiled-in modules: http_core.c mod_so.c mod_perl.c pwd? Syntax error on line 1141 of /usr/local/apache/conf/httpd.conf: Invalid command 'PerlHandler', perhaps mis-spelled or defined by a module not included in the server configuration [snip] Any adivce on this Tell us which of the httpd binaries on your system you're running 73, Ged. Hi thanks, I'm running the very latest versions and a new build: mod_perl-1.27 apache_1.3.26 (unix) I have also tried nearly all the build types presented at the mod_perl site but the result is always the same - mod_perl seems not to be recognized as being in the httpd binary!
RE: Compiled-in but not recognized
On Sun, 11 Aug 2002, Colin wrote: -Original Message- From: Ged Haywood [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 11, 2002 6:02 PM Subject: Re: Compiled-in but not recognized Hi there, On Sun, 11 Aug 2002, Colin wrote: I know this is a recurring problem but bear with me ... :) httpd -l Compiled-in modules: http_core.c mod_so.c mod_perl.c pwd? I think that Ged was suggesting you might have multiple httpd binaries on your system, and was suggesting that you verify you're running the binary you think you're running. It's really annoying when you're trying to debug a program, and the program you're running is not the one you're adding the debugging statements to. However, I suspect most of us have done it on occasion. Ed How the #@*! is it getting past all those debug statements without hitting any?!?! - Me
RE: Compiled-in but not recognized
Hi thanks, Yes I have established the server is running only 1 http binary so it is the correct one. Having tried almost all the build types from the mod_perl docs site (over 2 days!), the result is still the same. It works find via a DSO though. Perhaps if we start have a flood of similar problems then it would indicate a problem with the current versions of apache or mod_perl. I would hope ;) -Original Message- From: Ed Grimm [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 11, 2002 7:22 PM To: Colin Cc: [EMAIL PROTECTED] Subject: RE: Compiled-in but not recognized On Sun, 11 Aug 2002, Colin wrote: -Original Message- From: Ged Haywood [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 11, 2002 6:02 PM Subject: Re: Compiled-in but not recognized Hi there, On Sun, 11 Aug 2002, Colin wrote: I know this is a recurring problem but bear with me ... :) httpd -l Compiled-in modules: http_core.c mod_so.c mod_perl.c pwd? I think that Ged was suggesting you might have multiple httpd binaries on your system, and was suggesting that you verify you're running the binary you think you're running. It's really annoying when you're trying to debug a program, and the program you're running is not the one you're adding the debugging statements to. However, I suspect most of us have done it on occasion. Ed How the #@*! is it getting past all those debug statements without hitting any?!?! - Me
