Re: sed error in perl Makefile.pl

2003-01-03 Thread dom
 I have to rebuild my perl and go through the Configure
 process to tell it to ignore `hostname`, unless you
 know a trick for that, too!

 Well, what about creating a custom shell script named hostname,
turn it executable, and put it somewhere in your PATH ?

#!/bin/sh
echo darkstar.frop.org

-- 
Dominique QUATRAVAUX   Ingénieur développeur senior
01 44 42 00 35 IDEALX




[DIGEST] mod_perl digest 2002/11/18

2003-01-03 Thread jgsmith
--

  mod_perl digest
 
November 18, 2002 - December 29, 2002

--

Recent happenings in the mod_perl world...

  Sorry for the delay -- end of semester, etc.  I should be back on a
  weekly or bi-weekly schedule for now.

Features

  o mod_perl status
  o module announcements
  o available mod_perlers
  o mailing list highlights
  o conferences
  o links


mod_perl status

  o mod_perl
- stable: 1.27 (released June 1, 2002) [1]
- development: 1.27_01-dev [2]
  o Apache
- stable: 1.3.27 (released October 3, 2002) [3]
- development: 1.3.28-dev [4]
  o mod_perl 2.0
- beta: 1.99_07 (released September 27, 2002) [5]
- development: (from cvs) [6]
  o Apache 2.0
- stable: 2.0.43 (released October 3, 2002) [7]
  o Perl
- stable: 5.8.0 (released July 18, 2002) [8]
- development: none [9]


module announcements

  o Apache::AuthenNTLM 0.23 - provides Microsoft's NTLM
authentication for Apache [10]

  o Apache::PAR 0.01 - Provides support for Perl ARchive files in
mod_perl [11]

  o HTML::Mason 1.16 - Component-based web application environment [12]

  o HTTP::WebTest 2.00 - Tests and reports on remote web sites [13]

  o OpenInteract 1.55 - Extensible web application server [14]


available mod_perlers

  o Maryland/Baltimore/DC (USA) area [15]


mailing list highlights

  o Perl Cookbook mod_perl chapter [16]

  o libapreq-1.1 Release Candidate 2 [17]

  o Apache 2 and need for light-weight proxy [18]

  o Cookie-free authentication / sessions [19]

  o How Perl Powers Christmas [20]

  o Online Tonight - Bricolage [21]

  o References of mod_perl usage in financial institutions [22]

  o Ideas for limiting form submissions [23]


conferences

  o OsCON 2003 Call for Proposals [24]


links

  o The Apache/Perl Integration Project [25]
  o mod_perl documentation [26]
  o Apache modules on CPAN [27]
  o _Writing Apache Modules with Perl and C_ homepage [28]
  o _mod_perl Developer's Cookbook_ homepage [29]
  o mod_perl news and advocacy [30]
  o mod_perl list archives
  - modperl@ [31]
  - dev@ [32]
  - docs-dev@ [33]
  - advocacy@ [34]


happy mod_perling...

--James
[EMAIL PROTECTED]

--
[1] http://perl.apache.org/dist/
[2] http://cvs.apache.org/snapshots/modperl/
[3] http://www.apache.org/dist/httpd/
[4] http://cvs.apache.org/snapshots/apache-1.3/
[5] http://perl.apache.org/dist/mod_perl-1.99_04.tar.gz
[6] http://cvs.apache.org/snapshots/modperl-2.0/
[7] http://www.apache.org/dist/httpd/
[8] http://www.cpan.org/src/stable.tar.gz
[9] http://www.cpan.org/src/README.html

[10] http://mathforum.org/epigone/modperl/qualsmungvong
[11] http://mathforum.org/epigone/modperl/feecrimphand
[12] http://mathforum.org/epigone/modperl/fimslywu
[13] http://mathforum.org/epigone/modperl/treltrandpoo
[14] http://mathforum.org/epigone/modperl/berlskerlcend

[15] http://mathforum.org/epigone/modperl/slongjaxbrax

[16] http://mathforum.org/epigone/modperl/clenplandsol
[17] http://mathforum.org/epigone/modperl/lehjahshou
[18] http://mathforum.org/epigone/modperl/swermkoytrald
[19] http://mathforum.org/epigone/modperl/gainourah
[20] http://www.perl.com/pub/a/2002/12/18/hohoho.html
 http://mathforum.org/epigone/modperl/yerlhungquem
[21] http://mathforum.org/epigone/modperl/grerdfungfrox
[22] http://mathforum.org/epigone/modperl/zhungkheufyr
[23] http://mathforum.org/epigone/modperl/crumteuvox

[24] http://conferences.oreillynet.com/os2003/
 http://conferences.oreillynet.com/cs/os2003/create/e_sess

[25] http://perl.apache.org/
[26] http://perl.apache.org/docs/
[27] http://www.cpan.org/modules/by-module/Apache/
[28] http://www.modperl.com/
[29] http://www.modperlcookbook.org/
[30] http://www.take23.org/
[31] http://perl.apache.org/maillist/modperl.html#Searchable_Archives
[32] http://perl.apache.org/maillist/dev.html#Searchable_Archives
[33] http://perl.apache.org/maillist/docs-dev.html#Searchable_Archives
[34] http://perl.apache.org/maillist/advocacy.html#Searchable_Archives



Re: perl's system() w/ apache under win2k

2003-01-03 Thread Steve Hay
Terra Info wrote:


2) a probable answer anyhow-
[...] Check to see if the user you run apache under is allowed to 
interact with the desktop. It should be in the services CPL applet 
under the entry for that service. Check that and restart the service.

A related problem that I stumbled upon recently with a mod_perl program 
on WinNT is that the Win32::Shortcut module (used to create Windows 
shortcuts, a bit (but not much) like Unix links) doesn't work unless 
the Apache service is allowed to Interact with the Desktop.

- Steve




Need help with perl and ezmlm-web

2003-01-03 Thread Margo Poolak
Hello!
I have several problems that i dont know how to fix!

1) Im trying to make work the ezmlm-web but it gives me an error:
[Thu Jan 02 10:38:50 2003] [error] [client 10.1.6.235] Can't locate
Mail/Ezmlm.pm in @INC (@INC contains:
/usr/lib/perl5/5.8.0/i386-linux-thread-multi /usr/lib/perl5/5.8.0
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl) at
/usr/local/bin/ezmlm/ezmlm-web.cgi line 44.
[Thu Jan 02 10:38:50 2003] [error] [client 10.1.6.235] BEGIN
failed--compilation aborted at /usr/local/bin/ezmlm/ezmlm-web.cgi line 44.

I think this means that i dont have ezmlm propertly installed!

2) Oki trying to install ezmlm:
/home/listmg/pakid/Ezmlm-0.03
perl Makefile.PL
make  make test
make install
Gives me an error:
Can't use an undefined value as a HASH reference at
/usr/lib/perl5/5.8.0/ExtUtils/MakeMaker.pm line 457

Look's like a problem with perl...stupid as im trying to install perl
again(because i don't know what else could be done!)

3) Trying to install perl:
perl Makefile.PL MP_AP_PREFIX=/usr/local/apache2/

make[1]: Leaving directory
`/home/listmg/pakid/mod_perl-1.99_07/docs/api/mod_perl-2.0'
make[1]: Entering directory `/home/listmg/pakid/mod_perl-1.99_07/xs'
make[2]: Entering directory `/home/listmg/pakid/mod_perl-1.99_07/xs/APR'
make[3]: Entering directory `/home/listmg/pakid/mod_perl-1.99_07/xs/APR/APR'
gcc -c  -I/home/listmg/pakid/mod_perl-1.99_07/src/modules/perl
-I/home/listmg/pakid/mod_perl-1.99_07/xs -I/usr/local/apache2//include
-D_REENTRANT -D_GNU_SOURCE  -fno-strict-aliasing  -I/usr/include/gdbm
-DMOD_PERL -O2 -march=i386 -mcpu=i686   -DVERSION=\0.01\
-DXS_VERSION=\0.01\ -fpic
-I/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE   APR.c
Running Mkbootstrap for APR ()
chmod 644 APR.bs
rm -f ../../../blib/arch/auto/APR/APR.so
LD_RUN_PATH=/usr/lib gcc  -shared -L/usr/local/lib APR.o  -o
../../../blib/arch/auto/APR/APR.so   -L/usr/local/apache2//lib -lapr
-laprutil  
/usr/bin/ld: cannot find -lapr
collect2: ld returned 1 exit status
make[3]: *** [../../../blib/arch/auto/APR/APR.so] Error 1
make[3]: Leaving directory `/home/listmg/pakid/mod_perl-1.99_07/xs/APR/APR'
make[2]: *** [subdirs] Error 2
make[2]: Leaving directory `/home/listmg/pakid/mod_perl-1.99_07/xs/APR'
make[1]: *** [subdirs] Error 2
make[1]: Leaving directory `/home/listmg/pakid/mod_perl-1.99_07/xs'
make: *** [subdirs] Error 2

Now i don't know what those errors are?

I was trying to look inside the ld (/etc/ld.so.conf) but nothing do be done
there!

Thanks for any support!



Re: perl's system() w/ apache under win2k

2003-01-03 Thread Terra Info
Doh! I avoid doing system calls to external apps like the plague so I 
forget things like that.
Thanks for catching it,
Tom

Stas Bekman wrote:

Terra Info wrote:
[...]
 application. If you would like to take output from that application 
then
 you should write to STDOUT all text you want the perl application to 
see
 as a return value from your system() call or `` (backticks) call.

you probably meant qx(), as system doesn't return the sub-process'
STDOUT, but only the exec status.

__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com


--
-
Terra Novum Research
[EMAIL PROTECTED]
www.terranovum.com
(617) 923-4132

PO Box 362
Watertown, MA 02471-0362

Nothing's so loud,
as hearing when we lie;
the truth is not kind,
and you've said neither am I.
 - Glenn Philips





Apache::MP3

2003-01-03 Thread paul . barker



Hi All

This may be off topic but since it's Friday I thought I'd have a quick play and
install Apache::MP3.

I've built the module and followed the Apache config instructions on the web
site, but every time I try to access the /music location I get a 500 error and
the following line in error_log :

[Fri Jan  3 13:24:49 2003] [error] Can't locate object method new via package
Apache (perhaps you forgot to load Apache?) at
/opt/perl/lib/site_perl/5.6.1/Apache/MP3.pm line 80.

Any ideas why it's not working. I'm using other modules without issue.

Perl 5.6.1
Mod Perl 1.27
HPUX 11i

startup.pl

#!/usr/local/bin/perl -w
# to load this file when the server starts, add this to httpd.conf:
# PerlRequire /path/to/startup.pl

BEGIN{
        use Apache ();
        use lib Apache-server_root_relative('lib/site_perl/5.6.1');
}

# make sure we are in a sane environment.
$ENV{GATEWAY_INTERFACE} =~ /^CGI-Perl/ or die GATEWAY_INTERFACE not Perl!;

use Apache::Registry ();
use Apache::Constants();
use DBI ();
use DBD::mysql ();
use CGI qw(-compile :all);
use CGI::Application;
use GD;
use MP3::Info;
use Apache::MP3;

1;

Cheers

Paul



***
Important.
Confidentiality: This communication is intended for the above-named person and
may be confidential and/or legally privileged. Any opinions expressed in this
communication are not necessarily those of the company. If it has come to you
in error you must take no action based on it, nor must you copy or show it to
anyone; please delete/destroy and inform the sender immediately.

Monitoring/Viruses
Orange may monitor all incoming and outgoing emails in line with current
legislation.  Although we have taken steps to ensure that this email and
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure they are actually virus free.

Orange PCS Limited is a subsidiary of Orange SA and is registered in England No
2178917, with its address at St James Court, Great Park Road, Almondsbury Park,
Bradley Stoke, Bristol BS32 4QJ.
***




Re: Question on possible effects of mod_perl on mod_cgi

2003-01-03 Thread Terra Info
That was it. I redefined Sig{__WARN__} to drop all STDERR output and my 
script output everything it was supposed to and exited cleanly. Now 
there is another bug that undoubtedly came from my trying to track down 
the original issue...
Thanks. That saved me a ton of time.
Tom

Terra Info wrote:

Ugh! I checked the users list archives but I never checked the dev 
archives. I liked p5p back in the day because it was all one in the 
same. Chaos, but oddly efficient. Thanks for the pointer.
As for the docs, I freely admit I missed it. I was not looking for 
PerlRun stuff when I went through that migration piece (I was looking 
for a different project) so when I started dealing with this I did not 
remember seeing it, therefore in my warped mind it did not exist. 
Right now, int/0 looks perfectly fine to me. Anyhow, I doubt listing 
all of them would help, just add in Apache::PerlRun into the header so 
it reads The Apache::Registry and Apache::PerlRun Families (or ~) 
and that would get people's attention a little bit better.
Thanks,
Tom

Stas Bekman wrote:

OK, now it's clear, thanks for the explanation. FWIW, there were 
discussions of possible pipes read/write deadlocks in the current 
mod_cgi implementation in Apache 2.0, so you may experience just 
that. Check the httpd-dev list archives.

[...]

   * Given that, I noticed PerlRun was no longer prominintly displayed
 in the docs 



What made you think so? The PerlRun docs weren't touched for ages.


and the migration FAQ did not to my knowledge even touch on it.




Because all you have to do is to s/Apache::/ModPerl::/ for all 
registry handlers, which includes PerlRun. Do you think that it'll 
help to explicitly list them all?

__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com





--
-
Terra Novum Research
[EMAIL PROTECTED]
www.terranovum.com
(617) 923-4132

PO Box 362
Watertown, MA 02471-0362

They that can give up essential liberty to obtain a little 
temporary safety deserve neither liberty nor safety. 
Benjamin Franklin, 
Historical Review of Pennsylvania, 1759 




Re: Apache::MP3

2003-01-03 Thread asdf asdf
Paul

I do know know that in your startup.pl file, if you put:

BEGIN{
   use Apache ();
   use lib Apache-server_root_relative('lib/site_perl/5.6.1');
}

Then the path to the directory would be:
/usr/local/apache/lib/site_perl/5.6.1
or
Whever the server root for apache is.

The directory you are pointing to looks like the Perl installation.

That lib directive points to the location of your Apache modules.

That stands out, but maybe veterans of mod_perl will see what I am getting 
at. I have built custom modules in a directory structure like so

/usr/local/apache/perl/Apache/Header.pm

with my use lib being set to:
use lib Apache-server_root_realtive('perl');

So anything in the Apache namespace would be placed in the Apache directory. 
I hope to play with the Apache::MP3 module myself, but I believe it has to 
be put in this directory. If I am wrong, please, fellow perlMonks, correct 
me.

Michael Shirk




From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Apache::MP3
Date: Fri, 3 Jan 2003 13:37:10 +




Hi All

This may be off topic but since it's Friday I thought I'd have a quick play 
and
install Apache::MP3.

I've built the module and followed the Apache config instructions on the 
web
site, but every time I try to access the /music location I get a 500 error 
and
the following line in error_log :

[Fri Jan  3 13:24:49 2003] [error] Can't locate object method new via 
package
Apache (perhaps you forgot to load Apache?) at
/opt/perl/lib/site_perl/5.6.1/Apache/MP3.pm line 80.

Any ideas why it's not working. I'm using other modules without issue.

Perl 5.6.1
Mod Perl 1.27
HPUX 11i

startup.pl

#!/usr/local/bin/perl -w
# to load this file when the server starts, add this to httpd.conf:
# PerlRequire /path/to/startup.pl

BEGIN{
        use Apache ();
        use lib Apache-server_root_relative('lib/site_perl/5.6.1');
}

# make sure we are in a sane environment.
$ENV{GATEWAY_INTERFACE} =~ /^CGI-Perl/ or die GATEWAY_INTERFACE not 
Perl!;

use Apache::Registry ();
use Apache::Constants();
use DBI ();
use DBD::mysql ();
use CGI qw(-compile :all);
use CGI::Application;
use GD;
use MP3::Info;
use Apache::MP3;

1;

Cheers

Paul



***
Important.
Confidentiality: This communication is intended for the above-named person 
and
may be confidential and/or legally privileged. Any opinions expressed in 
this
communication are not necessarily those of the company. If it has come to 
you
in error you must take no action based on it, nor must you copy or show it 
to
anyone; please delete/destroy and inform the sender immediately.

Monitoring/Viruses
Orange may monitor all incoming and outgoing emails in line with current
legislation.  Although we have taken steps to ensure that this email and
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure they are actually virus 
free.

Orange PCS Limited is a subsidiary of Orange SA and is registered in 
England No
2178917, with its address at St James Court, Great Park Road, Almondsbury 
Park,
Bradley Stoke, Bristol BS32 4QJ.
***


_
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE* 
http://join.msn.com/?page=features/virus



Re: perl's system() w/ apache under win2k

2003-01-03 Thread Randy Kobes
On Fri, 3 Jan 2003, Stas Bekman wrote:

 Terra Info wrote:
  Two things: 1) this is not the list for this question.
  2) a probable answer anyhow-
 
 If that's a real pitfall and it's doomed to be a recurrent question, can 
 we please document this under win32/? Also, Randy, it seems that there 
 is whole lot of win32 issues which apply to all mod_perl versions (per 
 our faq discussion), so rather than duplicating them in 
 docs/1.0/os/win32 and docs/2.0/os/win32, we should probably have an area 
 for general win32 issues, e.g. docs/general/os/win32 and point to it 
 from both 1.0 and 2.0.

That's a good idea - there are general issues like that.
I'll look into creating this.

-- 
best regards,
randy




Internal redirect to method handler bug?

2003-01-03 Thread Dave Rolsky
A user on the Mason list reported a problem when the used an internal
redirect pointed at a location handled by Mason.  What was happening is
that the HTML::Mason::ApacheHandler module, which has a _method_ handler
sub (sub handler ($$)) was being called without a package name (just $r)
because of the internal redirect.

I tried to make a bare bones config that duplicated the problem, but my
really simple config worked just fine.  Does this bug ring any bells?


-dave

/*===
House Absolute Consulting
www.houseabsolute.com
===*/



[win32] large binary distributions

2003-01-03 Thread Randy Kobes
If you have trouble staying connected to get the (large) Win32
all-in-one binary packages, either Perl-5.8-win32-bin.exe
(Perl-5.8.0/Apache-2.0.43/mod_perl-1.99) or perl-win32-bin.exe
(Perl-5.6.1/Apache-1.3.27/mod_perl-1.27), from
ftp://theoryx5.uwinnipeg.ca/pub/other/, there's now corresponding
subdirectories
  ftp://theoryx5.uwinnipeg.ca/pub/other/Perl-5.8-win32-bin/
and
  ftp://theoryx5.uwinnipeg.ca/pub/other/perl-win32-bin/
containing these packages split across multiple files (of around
3 MB each). README.join contains directions for joining these
files back together; alternatively, if you already have Perl on
your system, the distinstall script found in these subdirectories
will fetch the split files and do the joining for you.

-- 
best regards,
randy kobes




RE: mod_perl make failed: cannot find -lapr

2003-01-03 Thread Steve Davis
Here is an update:

But before I begin, let me say thank you for both Stan Bekman and Randy
Kobes for your assistance.  So far, result was both good and bad.  The
original issue which I was facing appears to have been resolved.
Unfortunately, yet another problem has been created.  Hence, this
problem may branch into a new issue for which I have started a new
newsgroup thread.  

I would like to recap the measures which were taken for the benefit of
others.  So I'll discuss these points first.  This will show what fix
was used in order to resolve the initial problem.  Then I'll address the
new development.  Refer below section Still again, another option to
get the punch line.

Background:

To solve the original problem I was having, it appears as if a new set
of source was needed, or the it might be resolved by acquiring just
incremental changes.  I didn't' have a client edition of CVS on my
system, and I was trying to avoid bringing that package online.  But I
also can appreciate the difficulty of segregating non-CVS files from the
entire release just to fix the problem I was having.  So there seamed to
be merit bringing going through yet another learning curve.

The first set of alternatives:

So, therefore, it looked as if I had two options to choose from 1)
install CVS and get incremental code that way; or, 2) acquire an entire
'bleeding edge' software release.  This wouldn't be 1.99_07 but result
in acquiring the work in process edition-which was yet another item I
was trying to avoid.  

I did work with CVS to bring it on line.  (I did not have a CVS client
established.  I acquired the manuals, set up the environment variables,
learned the syntax, etc.  I stumbled for a while because I wasn't aware
the package needed to be 'init'(ialized) before it would work.  So
although I used the proper command line syntax, it gave me numerous
error messages.  I eventually got to the point where the code imported,
and the incremental updates were applied.  But regretfully, the
compilation still failed.

The comment I would make about this is having both a CVS and non-CVS
edition of source code available to the public is good.  At time it
maybe necessary to get the CVS code but for some this may turn out to be
somewhat of a headache to bring online.  Unfortunately, in my case, this
turn out to be yet another rabbit trail.  

Yet another alternative was considered:

At one point, to solve my problem, I tried to get another edition of
apr, in the hope it might resolve issues with incompatibilities between
software packages.  Perhaps, I could go forward or backward one resolve
to fix problems with the naming conventions.

At least on my own system, conflicts were created with I downloaded the
latest edition of apr.  When this was compiled, I was no longer was I
able to recompile apache and the issues with mod_perl compiling were not
resolved.  There appears to be a conflict with apache 2.0.43 with
apr-0.9.2.  Now things were definitely getting worse.  Now web server
was offline too and an important library directory had incompatible
libraries in it.  I lost territory.

And I not so sure there is an issue with naming conventions after all,
for I tried to use an earlier edition of apr dating back to august and
it problems still existed.  Further, between the different apr
compilations the naming conventions did not change.  I could investigate
this further but I am not it would be worth the energy.  Changes may
have occurred but not with the source for which I was working with.

Still again, another option:  

Then I hunted and pecked for a while for another alternative.  (At this
point, I was on a mission.  Some minds are like finished cement,
thoroughly mixed and permanently set.  I would really like to get this
online.)  Finally, I discovered http://cvs.apache.org/snapshots/ and it
was from this resource for which I able to get an easier solution.  The
is a different source rather than that found under
http://perl.apache.org/dist/ and provided from
http://perl.apache.org/download/source.html#2_0_Development_Source_Distr
ibution 

Finally, a step in the right direction:

I don't know if the is a difference between the distribution source vs.
that found in the CVS source, or it there just happened to be recent
changes (directories/links to these files), but there is a change in the
outcome than what I was first working with.  Through this new resource,
I downloaded an entire software release and began to work with that.
Fortunately, I was able to compile mod_perl.  Progress at last!
Working with mod_perl 2.0 was definitely better than edition 1.99_07.

The bad news:

But now a new problem has developed-the bad news.  When httpd.conf
configured to invoke the new mod_perl module, and when httpd is started,
Apache is generates the following error message httpd failed. The error
was: Starting httpd: httpd: module mod_perl.c is not compatible with
this version of Apache.  Please contact the vendor for the correct
version.

mod_perl.c Not Compatible with Apache

2003-01-03 Thread Steve Davis
Upon successfully compiling mod_perl 2.0, and modifying httpd.conf so
that it becomes invoked at the start of Apache 2.0.43, the following
error message is gernerated.  It is httpd failed. The error was:
Starting httpd: httpd: module mod_perl.c is not compatible with this
version of Apache.
Please contact the vendor for the correct version. [FAILED]

If you would like you, may refer to the previous thread named mod_perl
make failed: cannot find -lapr for a history of the root of this
problem-particularly the last post directly before this article.  This
also shows the detail environment and configuration for the server in
question.  Else, I would be glad more details to this post.  In brief,
let me say, the system consists of RH 8.0, apache 2.0.43, and current
CVS edition of mod_perl 2.0.  It has a date stamp of 1/1/03.

This is one problem which I don't know how to proceed with.  Is this
message saying the code in mod_perl's mod_perl.c is using an edition
of 'C' code that is incompatible with Apache 2.0?  Is the development
environment for which mod_perl 2.0 is being developed, by its creators,
using a 'C' compiler that is different than what is found on RH 8.0?
Does any one have an idea of how I might go about solving this problem?
Any advance given would be appreciated.  

Steve D







Re: mod_perl.c Not Compatible with Apache

2003-01-03 Thread Randy Kobes
On Fri, 3 Jan 2003, Steve Davis wrote:

 Upon successfully compiling mod_perl 2.0, and modifying httpd.conf so
 that it becomes invoked at the start of Apache 2.0.43, the following
 error message is gernerated.  It is httpd failed. The error was:
 Starting httpd: httpd: module mod_perl.c is not compatible with this
 version of Apache.
 Please contact the vendor for the correct version. [FAILED]
 
 If you would like you, may refer to the previous thread named mod_perl
 make failed: cannot find -lapr for a history of the root of this
 problem-particularly the last post directly before this article.  This
 also shows the detail environment and configuration for the server in
 question.  Else, I would be glad more details to this post.  In brief,
 let me say, the system consists of RH 8.0, apache 2.0.43, and current
 CVS edition of mod_perl 2.0.  It has a date stamp of 1/1/03.
 
 This is one problem which I don't know how to proceed with.  Is this
 message saying the code in mod_perl's mod_perl.c is using an edition
 of 'C' code that is incompatible with Apache 2.0?  Is the development
 environment for which mod_perl 2.0 is being developed, by its creators,
 using a 'C' compiler that is different than what is found on RH 8.0?
 Does any one have an idea of how I might go about solving this problem?
 Any advance given would be appreciated.  

I think in general the problem
  mod_perl.c is not compatible with this version of Apache.
means that mod_perl was compiled against a different set of
Apache sources than that used to build the server trying to
load the mod_perl module (assuming that the same compiler
is being used in building Perl, Apache, and mod_perl).

Just to clarify what came from where 

- are you using a modperl-2.0 cvs snapshot from
 http://cvs.apache.org/snapshots/modperl-2.0/?
- are you running Apache 2.0.43, compiled from the sources
  httpd-2.0.43.tar.gz from 
 http://httpd.apache.org/dist/httpd/?

If so, does modperl-2.0 compile against these apache 2.0 sources
successfully?

-- 
best regards,
randy




RE: mod_perl.c Not Compatible with Apache

2003-01-03 Thread Steve Davis
Randy,

All of what I've done, in the form of compiling software, has been done
on the same computer and with the same release of the RH.  So, there is
nothing for which I'm doing to distinctly change which compiler is being
used between the compilations of the packages.

As best as I can recall, the answer is 'yes' to the last three questions
you asked.  1) Everything compiles successfully.  2) The edition of
mod_perl was obtained from cvs.apache.org while the Apache was from the
distribution source repository.  3) The various release numbers for the
packages where the most current; hence, 2.0.43 of Apache and 2.0 for
mod_perl.

Maybe there is some difference between the distribution and CVS versions
of Apache.  Perhaps, the next step will be to match packages via
obtaining CVS editions from both packages and see what happens then.
This shouldn't take to long.  I'll give it a shot and provide an update.


Let me also add, I'm grateful for your help.  Thank you.

Steve D

The following comments were provided from Randy Kobes:

I think in general the problem  mod_perl.c is not compatible with this
version of Apache.
means that mod_perl was compiled against a different set of Apache
sources than that used to build the server trying to load the mod_perl
module (assuming that the same compiler
is being used in building Perl, Apache, and mod_perl).

Just to clarify what came from where 

- are you using a modperl-2.0 cvs snapshot from
 http://cvs.apache.org/snapshots/modperl-2.0/?
- are you running Apache 2.0.43, compiled from the sources
  httpd-2.0.43.tar.gz from 
 http://httpd.apache.org/dist/httpd/?

If so, does modperl-2.0 compile against these apache 2.0 sources
successfully?

-- 
best regards,
randy






RE: mod_perl.c Not Compatible with Apache

2003-01-03 Thread Steve Davis
Randy,

You 'maybe' on to something here.  Let me report to you what I found.
In order to be as careful and consistent as possible, I've actually
started to keep a log of my activities.  It records which commands which
I've been used to compile the packages.  So I can saw with certainty the
following.  Here are the parameters which I used to compile both Apache
and mod_perl.

To configure Apache:
./configure --prefix=/etc/httpd --with-mpm=prefork

To configure mod_perl:
perl Makefile.PL MP_AP_PREFIX=/etc/httpd MP_APXS=/etc/httpd/bin/apxs
MP_INST_APACHE2=1 MP_DEBUG=1

Also, when I examine /etc/httpd/bin/httpd (the executable),
/etc/httpd/lib/libarp*,  and /etc/module/mod_perl.so, all the theses
files have a creation date that's current (today's date).  Plus,
/etc/httpd/httpd.conf points to the current file locations.  According
to the RH 8.0 docs regarding Apache 2.X, they suggest modifying
httpd.conf to incorporate the use of an include statement which invokes
/etc/conf.d/perl.conf.  This latter file points to
/etc/httpd/module/mod_perl.3.0.  I've mapped the files and dates.  There
doesn't appear to be any conflict here.  

However, for good measure, I just completed a search of the /etc/* and
/usr/* directories for the presence of the httpd executable.  And there
are two of them on the system.  To be expected, the /etc/httpd/bin/httpd
executable is present.  However, these is also an existence of a httpd
executable under /usr/sbin.  When I changed the name of /etc/sbin/httpd
to /etc/sbin/httpd-bu (backup).  The httpd web server wouldn't start any
longer (I toggled this off and on via the service utilility [start -
system settings - service]).  /etc/sbin/httpd has a footprint of 384.7K
where as /etc/httpd/bin/httpd is a 2meg file.  I don't know whether
/etc/sbin/httpd is being used to merely start /etc/httpd/bin/httpd or
not.  If you can advise further it would be helpful.

This is the first time which I had to gain the merits (and subsequent
challenges) of dealing with the open source world.  Bringing mod_perl
on-line has been a bitter-sweet experience.  On the up side, it is
certainly sweet to gain help from others for which I am exceedingly
grateful for.  In this regard, the help being provided is making this a
better experience.  To your credit, I not accustom to this type of aid
when dealing with the proprietary world.  That is, I am not familiar
with receiving the same degree of cooperation, support, and camaraderie.
Therefore, let me continue to express my gratitude.  It means a lot to
me.  Thank you.  

Steve


Steve D


-Original Message-
From: Randy Kobes [mailto:[EMAIL PROTECTED]] 
Sent: Friday, January 03, 2003 5:19 PM
To: Steve Davis
Cc: [EMAIL PROTECTED]
Subject: RE: mod_perl.c Not Compatible with Apache 

On Fri, 3 Jan 2003, Steve Davis wrote:

 Randy,
 
 All of what I've done, in the form of compiling software, has been
done
 on the same computer and with the same release of the RH.  So, there
is
 nothing for which I'm doing to distinctly change which compiler is
being
 used between the compilations of the packages.
 
 As best as I can recall, the answer is 'yes' to the last three
questions
 you asked.  1) Everything compiles successfully.  2) The edition of
 mod_perl was obtained from cvs.apache.org while the Apache was from
the
 distribution source repository.  3) The various release numbers for
the
 packages where the most current; hence, 2.0.43 of Apache and 2.0 for
 mod_perl.
 
 Maybe there is some difference between the distribution and CVS
versions
 of Apache.  Perhaps, the next step will be to match packages via
 obtaining CVS editions from both packages and see what happens then.
 This shouldn't take to long.  I'll give it a shot and provide an
update.

This is strange ... I just tried, on a RedHat 7.1 system, the
cvs modperl-2.0 sources compiled against
Server version: Apache/2.0.43
built using stock httpd-2.0.43 sources, and it went fine. You 
shouldn't have to use the cvs apache sources. mod_perl was built as
 perl Makefile.PL MP_AP_PREFIX=/usr/local/httpd MP_INST_APACHE2=1
where the httpd binary is installed under /usr/local/httpd/bin. 

One thought ... Some Linux distributions come with their own
Apache server, which may be in a different location than the
Apache 2.0.43 you built and installed. Are you sure that the
mod_perl you built is being used with your Apache-2.0.43
specified under MP_AP_PREFIX?

-- 
best regards,
randy






Re: Need help with perl and ezmlm-web

2003-01-03 Thread Stas Bekman
Margo Poolak wrote:

Hello!
I have several problems that i dont know how to fix!

1) Im trying to make work the ezmlm-web but it gives me an error:

[...]

2) Oki trying to install ezmlm:
/home/listmg/pakid/Ezmlm-0.03
perl Makefile.PL
make  make test
make install
Gives me an error:
Can't use an undefined value as a HASH reference at
/usr/lib/perl5/5.8.0/ExtUtils/MakeMaker.pm line 457

Look's like a problem with perl...stupid as im trying to install perl
again(because i don't know what else could be done!)


These two has nothing to do with mod_perl, please take them to one of 
the lists at http://lists.perl.org

3) Trying to install perl:
perl Makefile.PL MP_AP_PREFIX=/usr/local/apache2/

make[1]: Leaving directory
`/home/listmg/pakid/mod_perl-1.99_07/docs/api/mod_perl-2.0'
make[1]: Entering directory `/home/listmg/pakid/mod_perl-1.99_07/xs'
make[2]: Entering directory `/home/listmg/pakid/mod_perl-1.99_07/xs/APR'
make[3]: Entering directory `/home/listmg/pakid/mod_perl-1.99_07/xs/APR/APR'
gcc -c  -I/home/listmg/pakid/mod_perl-1.99_07/src/modules/perl
-I/home/listmg/pakid/mod_perl-1.99_07/xs -I/usr/local/apache2//include
-D_REENTRANT -D_GNU_SOURCE  -fno-strict-aliasing  -I/usr/include/gdbm
-DMOD_PERL -O2 -march=i386 -mcpu=i686   -DVERSION=\0.01\
-DXS_VERSION=\0.01\ -fpic
-I/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE   APR.c
Running Mkbootstrap for APR ()
chmod 644 APR.bs
rm -f ../../../blib/arch/auto/APR/APR.so
LD_RUN_PATH=/usr/lib gcc  -shared -L/usr/local/lib APR.o  -o
../../../blib/arch/auto/APR/APR.so   -L/usr/local/apache2//lib -lapr
-laprutil  
/usr/bin/ld: cannot find -lapr
collect2: ld returned 1 exit status
make[3]: *** [../../../blib/arch/auto/APR/APR.so] Error 1
make[3]: Leaving directory `/home/listmg/pakid/mod_perl-1.99_07/xs/APR/APR'
make[2]: *** [subdirs] Error 2
make[2]: Leaving directory `/home/listmg/pakid/mod_perl-1.99_07/xs/APR'
make[1]: *** [subdirs] Error 2
make[1]: Leaving directory `/home/listmg/pakid/mod_perl-1.99_07/xs'
make: *** [subdirs] Error 2

Now i don't know what those errors are?

You need to use the latest cvs version or wait for the new version to be 
released, which should happen RSN.
http://perl.apache.org/download/source.html#2_0_Development_Source_Distribution
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com



Re: mod_perl.c Not Compatible with Apache

2003-01-03 Thread Stas Bekman
I've updated the README file to specify the minimum and maximum Apache 
versions required, the next mod_perl version's release will include it.

As for your troubles, as Randy has suggested you probably have a bunch 
of various installs laying around and you've it all messed up. You don't 
need to install apr separately from Apache, just grab the latest cvs 
version of Apache and mod_perl, build them and you will be all set. See:
http://perl.apache.org/docs/2.0/user/install/install.html#Getting_Bleeding_Edge_CVS_Sources
http://perl.apache.org/docs/2.0/user/install/install.html#Configuring_and_Installing_Prerequisites
http://perl.apache.org/docs/2.0/user/install/install.html#Downloading_the_mod_perl_Source
...

It should just work. To make sure that you aren't messing up with other 
installation on your system, go and clean those up first.

__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com



Re: Internal redirect to method handler bug?

2003-01-03 Thread Dave Rolsky
On Fri, 3 Jan 2003, Dave Rolsky wrote:

 A user on the Mason list reported a problem when the used an internal
 redirect pointed at a location handled by Mason.  What was happening is
 that the HTML::Mason::ApacheHandler module, which has a _method_ handler
 sub (sub handler ($$)) was being called without a package name (just $r)
 because of the internal redirect.

 I tried to make a bare bones config that duplicated the problem, but my
 really simple config worked just fine.  Does this bug ring any bells?

Aha!  I just found this in the archives (which I looked at before posting,
but not carefully enough):

http://marc.theaimsgroup.com/?l=apache-modperlm=101236133418008w=2

The above message says this happened with version 1.25  1.26, but the
Mason user who reported the problem is using 1.27, so it hasn't been fixed
yet.


-dave

/*===
House Absolute Consulting
www.houseabsolute.com
===*/



RE: mod_perl.c Not Compatible with Apache

2003-01-03 Thread Randy Kobes
On Fri, 3 Jan 2003, Steve Davis wrote:

[ .. ]
 To configure Apache:
 ./configure --prefix=/etc/httpd --with-mpm=prefork
 
 To configure mod_perl:
 perl Makefile.PL MP_AP_PREFIX=/etc/httpd MP_APXS=/etc/httpd/bin/apxs
 MP_INST_APACHE2=1 MP_DEBUG=1
 
 Also, when I examine /etc/httpd/bin/httpd (the executable),
 /etc/httpd/lib/libarp*, and /etc/module/mod_perl.so, all the
 theses files have a creation date that's current (today's
 date).  Plus, /etc/httpd/httpd.conf points to the current file
 locations.  According to the RH 8.0 docs regarding Apache 2.X,
 they suggest modifying httpd.conf to incorporate the use of an
 include statement which invokes /etc/conf.d/perl.conf.  This
 latter file points to /etc/httpd/module/mod_perl.3.0.  I've
 mapped the files and dates.  There doesn't appear to be any
 conflict here.
 
 However, for good measure, I just completed a search of the
 /etc/* and /usr/* directories for the presence of the httpd
 executable.  And there are two of them on the system.  To be
 expected, the /etc/httpd/bin/httpd executable is present.  
 However, these is also an existence of a httpd executable under
 /usr/sbin.  When I changed the name of /etc/sbin/httpd to
 /etc/sbin/httpd-bu (backup).  The httpd web server wouldn't
 start any longer (I toggled this off and on via the service
 utilility [start - system settings - service]).  
 /etc/sbin/httpd has a footprint of 384.7K where as
 /etc/httpd/bin/httpd is a 2meg file.  I don't know whether
 /etc/sbin/httpd is being used to merely start
 /etc/httpd/bin/httpd or not.  If you can advise further it
 would be helpful.

It sounds like /etc/sbin/httpd and /etc/httpd/bin/httpd are
separate binaries, judging by their different sizes. You
compiled modperl against /etc/httpd/bin/httpd, but your system
is using /etc/sbin/httpd in the services utility to start.
This might explain the problem you were having before - 
/etc/sbin/httpd might be an older apache binary from
before (perhaps the installation), whereas mod_perl was
compiled against the newer /etc/httpd/bin/httpd. It's
hard to tell whether or not the binaries are sharing
the same httpd.conf files.

Did mod_perl's 'make test' pass? When you start the test,
it reports which httpd it's using - is it /etc/httpd/bin/httpd?

One thing you might try - stop the /etc/sbin/httpd service,
and then go to /etc/httpd/bin and issue the command
apachectl start
to start the server associated with /etc/httpd/. This (normally)
will use the httpd.conf under /etc/httpd/conf/, which presumably
is the right one - if not, try starting httpd with the -f switch
to specify the config file - see ./httpd -h for help. 
Alteratively, since you have a backup of /etc/sbin/httpd,
try copying /etc/httpd/bin/httpd to /etc/sbin/httpd, and
start the service.

Do either of these work? If so, what you might do is forget
completely about the httpd stuff under /etc (which sounds like
it's getting mixed up with different versions), and compile
httpd-2.0.43 using a prefix like /usr/local/httpd, and then
compile and install mod_perl against this prefix. With a fresh
install Apache will install a reasonable default httpd.conf.  
You'd then have to figure out how to adjust the service utility
to start /usr/local/httpd/bin/httpd, rather than /etc/sbin/httpd.

-- 
best regards,
randy