I actually was successful at building apache/mod_perl static with DSO
support and not having to change the rest of the modules. It appears to
be working, so will continue to test further.
Greg
* Drew Taylor ([EMAIL PROTECTED]) [020728 22:19]:
> There are well written instructions in The Guide t
In preparation for some other work I'm doing, I have added some features
and fixed some bugs in Uttu:
o Added support for AxKit as a content handler. The handler allows
using either HTML::Mason or Template Toolkit as an XML provider
with a simple configuration setting.
o Made the co
There are well written instructions in The Guide that show step by step how
to roll a static mod_perl/php/ssl binary. And I've done it personally
without much trouble, so it's easier than you might think. ;-) Here's the
direct link:
http://perl.apache.org/docs/1.0/guide/install.html#mod_perl_an
Yup, this is it. If I build it without DSO support, it appears to work.
Of course I build this with mod_php, mod_ssl, mod_perl, and a couple of
custom modules. So running without DSO support isn't to easy. I guess
I can attempt to build mod_perl in, but keep DSO support and dynamic
load the res
Hey Greg et al.
I'd betcha your problem is almost certainly caused by your use of DSOs. If
you *really* want to prune your system down to see where your bug is, then
build apache and mod_perl statically. There was a very well-known bug that
caused DBI to segfault if it was run under a DSO. Ple
At 06:20 AM 28/07/2002 -0700, you wrote:
>Hello,
> I have got some problems when I tried to install
>Apache server together with mod_perl and Apache::ASP.
>After I had located four subfolder to c:/ , which
>mean, I have got c:/perl, c:/apache, c:/openssl,
>c:/readmes.
>When I tried to start apac
What does 'Constants.lib' look like? Does it have a 'package' statement?
Does it use Exporter?
If it's a package then unless you've got some magic in 'Constants.lib',
that BEGIN block will not pull the constants into the current package -
the 'import' call is missing. (See perldoc -f use)
If it
Hi there,
On Sun, 28 Jul 2002, allan juul wrote:
> i wish to use use constants defined in a seperate file. my problem is, that
> sometimes it works sometimes it doesn't. when failing, the error_log says
> Bareword is not allowed so i guess it sometimes never loads my constants file
> at all.
Hi All,
I have a situation where it is convinent for me to define a global
"PerlSetVar" in my httpd.conf and then unset it for particular virtual
hosts.
I used to use the following configuration successfully:
httpd.conf
--
use A
Hi there folks,
I'm just getting back into some mod_perl after a fairly lengthy absence,
and I'm running into some troubles with cookies.
Basic summary- I'm trying to set a session ID in a cookie, and it works only
if I do not include an expiration time.
Details:
-snip
How is your mod_perl configured? Based on the error message you're
getting, it appears that you may not have compiled in support for
authentication or access control.
If you built it yourself, you may need to add PERL_AUTHEN=1 and
PERL_ACCESS=1 to the 'perl Makefile.PL' command line when buildin
* David Kaufman ([EMAIL PROTECTED]) [020728 00:55]:
> again, just a shot in the dark, but why not try the more mod_perl specific
> Apache::DBI instead of plain ole DBI?
Okay I have tried this. I also edited the Apache/DBI.pm and enabled
both Apache::DBI and DBI debugging at level 2 so I could ge
Hello,
I have got some problems when I tried to install
Apache server together with mod_perl and Apache::ASP.
After I had located four subfolder to c:/ , which
mean, I have got c:/perl, c:/apache, c:/openssl,
c:/readmes.
When I tried to start apache.exe. There is an error
message showing that it
hi
i wish to use use constants defined in a seperate file. my problem is, that
sometimes it works sometimes it doesn't. when failing, the error_log says
Bareword is not allowed so i guess it sometimes never loads my constants file
at all.
this is my basic approach:
Package Foo:Bar;
use str
"Greg Rumple" <[EMAIL PROTECTED]> wrote:
> The test.pl script works fine by it's self. Turning on full PERL
> debugging/tracing yields that the actual script has fully finished, and
> that it's in the tear down of the actualy perl stuff that this failure
> is coming from. Not from the script p
15 matches
Mail list logo
