Makefile.PL bug (?) - USE_APXS/DYNAMIC incompatible

2001-01-27 Thread Lynn Winebarger
Ok, I resolved this. It appears USE_APXS is incompatible with DYNAMIC, producing the results I posted previously. I don't know whether this reflects a true incompatibility in the code or not. Someone might want to add a warning - particularly since DYNAMIC is the only switch that turns on al

Re: make problem - mod_perl.h not found by Apache::modules (more)

2001-01-27 Thread Lynn Winebarger
A little more on my configuration - I've got both a /usr/ install of perl (5.005) and 5.6.0 installed in /usr/local/perl (for chrooting purposes). I also have /usr/local install of apache 1.3.12 and a /usr/local/apache install of 1.3.14 (again, for chrooting). The attempt below was trying to

Re: Error message --> out of free buffers:

2001-01-27 Thread Buddy Lee Haystack
Sorry for the post. It appears to be a PostgreSQL configuration issue, and not an Apache/mod_perl issue.

Re: Making PHP and mod_perl live together in Apache 1.3.14.

2001-01-27 Thread Martin Langhoff
Mr Wells, I have succesfully built them together following this procedure. I am also including mysql and imap support in PHP. Be aware that many lines that should be a 'one-liner' have been broken by my mailer. untar apache 1.3.12, mod_perl 1.24, php 4.0.3 and c-client (from uw) # build imap c

Re: [DIGEST] mod_perl digest 01/01/2001

2001-01-27 Thread Ask Bjoern Hansen
On Tue, 9 Jan 2001, Geoffrey Young wrote: What happened to the weekly digests? > o Apache > - stable: 1.3.14 (released October 13, 2000) [3] > - development: 1.3.15-dev [4] 1.3.17 is about to be released, .15 and .16 were skipped. -- ask bjoern hansen -

Error message --> out of free buffers:

2001-01-27 Thread Buddy Lee Haystack
I receive the following error message in my Apache error_log after pressing the submit button in "machine-gun like fashion" on one of my forms that requires roughly a minute to process each request using Apache::DBI, mod_perl and PostgreSQL. [Sat Jan 27 15:03:07 2001] null: DBD::Pg::st execut

Re: Making PHP and mod_perl live together in Apache 1.3.14.

2001-01-27 Thread G.W. Haywood
Hi there, On Sat, 27 Jan 2001, wells wrote: > Thanks for the reply.. is there a URL where I can view the archives > of Support? I think there's a misunderstanding here. SUPPORT is the name of a file in your mod_perl directory, right alongside README... The several archives of the mod_perl Mai

mod_perl as DSO on AIX with perl-5.6

2001-01-27 Thread Christian Gilmore
Hey. I see in mod_perl's INSTALL document that there's a required patch for DynaLoader if you intend to run mod_perl as DSO on AIX (4.3) with perl-5.005_3. Is patching required for 5.6? If so, will the same patch in the INSTALL doc apply? Regards, Christian - Christian Gilmore In

Re: Making PHP and mod_perl live together in Apache 1.3.14.

2001-01-27 Thread G.W. Haywood
Hi there, On Sat, 27 Jan 2001, wells wrote: > I'm having loads of trouble geting PHP (either as a dynamic SO or a static > SO) to live peacefully with mod_perl 1.24_10. if they are both compiled in > the httpd binary, then apache causes segmenation faults. > > any ideas on how to work around

Making PHP and mod_perl live together in Apache 1.3.14.

2001-01-27 Thread wells
I'm having loads of trouble geting PHP (either as a dynamic SO or a static SO) to live peacefully with mod_perl 1.24_10. if they are both compiled in the httpd binary, then apache causes segmenation faults. any ideas on how to work around this? / wells // [EMAIL PROTECTED] " i saved latin. wha

Re: Apache Version 1.3.0 required, aborting... You need mod_perl 1.24_01 , or later to build with Apache 1.3.14

2001-01-27 Thread G.W. Haywood
Hi Cliff, On Sat, 27 Jan 2001, ___cliff rayman___ wrote: > ged - you are just plain wrong here. > the error message is very clear. u just need to install > apache 1.3.0. to hell with bugs and security problems. > newer software is just bloated and cpu hungry anyways. > > well, now i'll get pa

Re: Apache Version 1.3.0 required, aborting... You need mod_perl 1.24_01 , or later to build with Apache 1.3.14

2001-01-27 Thread ___cliff rayman___
ged - you are just plain wrong here. the error message is very clear. u just need to install apache 1.3.0. to hell with bugs and security problems. newer software is just bloated and cpu hungry anyways. well, now i'll get pack to my port of perl 4, mod_perl, and apache 1.3.0 for the TRS-80. cl

ANNOUNCE: TPC5 Call for Papers

2001-01-27 Thread Ask Bjoern Hansen
Hi, Just a reminder that the deadline for sending proposals is coming up. http://perl.apache.org/conferences/tpc5-us/cfp.html [EMAIL PROTECTED] is waiting for *YOUR* proposal. :-) - ask -- ask bjoern hansen -

Re: XML & subrequest

2001-01-27 Thread Matt Sergeant
On Sat, 27 Jan 2001, Antti Linno wrote: > Hallo. > > I have a problem. I was writing a Apache module, that would generate a > form, then gather and check the form data, send it to a second server and > get a xml page for an answer. What I need now, is to parse somehow this > xml content and retur

make problem - mod_perl.h not found by Apache::modules

2001-01-27 Thread Lynn Winebarger
Hi. I'm having problems getting mod_perl (1.24<_01>) to compile. I'm using perl 5.6.0, apache 1.3.14, RH Linux 6.2/Intel (with upgrades). This is odd since I've previously built mod_perl successfully as a DSO (and the problem appears to be in the configure - I don't get far enough in the make

XML & subrequest

2001-01-27 Thread Antti Linno
Hallo. I have a problem. I was writing a Apache module, that would generate a form, then gather and check the form data, send it to a second server and get a xml page for an answer. What I need now, is to parse somehow this xml content and return user a html page. Somebody told me to use subreque

Apache Version 1.3.0 required, aborting... You need mod_perl 1.24_01 , or later to build with Apache 1.3.14

2001-01-27 Thread G.W. Haywood
Hey guys, Even google knew the answer to this one. See http://www.mail-archive.com/modperl%40apache.org/msg12607.html I thought if I put the error message AND the solution in the subject line, with a slightly sarcastic message, and then everybody flamed me (being careful to keep the subject line