compilation output when using modperl ?
Hi erveryone,
I am using modperl2 with apache2 on win32 (activestate Perl 5.8). I
have my own perl module included in the apache conf.
Whenever I have an error in my module apache does not start and the
only error message I can find is in apache's error.log
William A. Rowe, Jr. schrieb:
Alvar Freude wrote:
Hi,
-- Jens Helweg [EMAIL PROTECTED] wrote:
Is there a way to get the compilers output from perl, so I can get
details on what is wrong in the code ?
usually you get the errors in the apache's error log. I don't know where
it is stored on
Michael Peters schrieb:
Jens Helweg wrote:
How do the modperl pros find an error in modperl modules when all apache
tells is that it can't load the module instead of priting the complete
error that the perl compiler/parser has with the code.
I'm not sure why the error message is getting
John ORourke schrieb:
Jens Helweg wrote:
I thought perl -c mymodule.pm is no option when developing modperl
handler modules because these will only run/build in the apache
modperl environment and not on command line ?
Not sure about your windows environment but a command-line perl -c works
stuff from my code.
I never investigated so as to get the true perl diagnose.
Lionel.
- Original Message -
From: Jens Helweg [EMAIL PROTECTED]
To: modperl@perl.apache.org
Sent: Thursday, June 28, 2007 12:09 PM
Subject: Where is Perl compilation output when using modperl ?
Hi
Hi erveryone,
I am using modperl2 with apache2 on win32 (activestate Perl 5.8). I have
my own perl module included in the apache conf.
Whenever I have an error in my module apache does not start and the only
error message I can find is in apache's error.log:
Can't load Perl file:
On Thu, 28 Jun 2007, Jens Helweg wrote:
Hi erveryone,
I am using modperl2 with apache2 on win32 (activestate Perl 5.8). I have my
own perl module included in the apache conf.
Whenever I have an error in my module apache does not start and the only
error message I can find is in apache's
Randy Kobes schrieb:
On Thu, 28 Jun 2007, Jens Helweg wrote:
Hi erveryone,
I am using modperl2 with apache2 on win32 (activestate Perl 5.8). I
have my own perl module included in the apache conf.
Whenever I have an error in my module apache does not start and the
only error message I can
Jens Helweg wrote:
How do the modperl pros find an error in modperl modules when all apache
tells is that it can't load the module instead of priting the complete
error that the perl compiler/parser has with the code.
I'm not sure why the error message is getting buried for you, but I get
Jens Helweg wrote:
I thought perl -c mymodule.pm is no option when developing modperl
handler modules because these will only run/build in the apache
modperl environment and not on command line ?
Not sure about your windows environment but a command-line perl -c works
just fine for me on
Hi,
-- Jens Helweg [EMAIL PROTECTED] wrote:
Is there a way to get the compilers output from perl, so I can get
details on what is wrong in the code ?
usually you get the errors in the apache's error log. I don't know where
it is stored on Windows, you may look in your httpd.conf.
Ciao
Alvar Freude wrote:
Hi,
-- Jens Helweg [EMAIL PROTECTED] wrote:
Is there a way to get the compilers output from perl, so I can get
details on what is wrong in the code ?
usually you get the errors in the apache's error log. I don't know where
it is stored on Windows, you may look in
12 matches
Mail list logo
