You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Anuradha Satyanarayana <as...@ascend.com> on 2001/05/03 09:28:57 UTC
unable to makefile of the modperl
Unable to make the modperl Makefile.PL downloaded from perl.apache.org.
throwing errors like the following:
Checking for LWP::UserAgent......failed
Can't locate HTTP/Request.pm in @INC at lib/LWP/UserAgent.pm line 97.
BEGIN failed--compilation aborted at lib/LWP/UserAgent.pm line 97.
The libwww-perl library is needed to run the test suite.
Installation of this library is recommended, but not required.
Checking for HTML::HeadParser....failed
Can't locate HTML/HeadParser.pm in @INC at Makefile.PL line 1129.
Can anyone help?
Regds
Anuradha
Re: Throwing die in Apache::Registry
Posted by Stas Bekman <st...@stason.org>.
On Fri, 4 May 2001, Mark Maunder wrote:
> Hi,
>
> I'm sure this has been discussed, appologies if it has, but I scoured the lists
> and docs and didn't get any help.
>
> I have an Apache::Registry script that is using XML::Parser. The parser throws a
> 'die' call if it encounters a parse error (Why?). I was handling this by putting
> the code in an eval block, but this no longer works since all Registry scripts
> are already in one huge eval block. So whenever I get a parse error, my code
> ignores my eval block which encapsulates it and jumps to the end of the Registry
> eval block and effectivelly exits. How does one 'eval' code that might call 'die'
> under Apache::Registry?
http://perl.apache.org/guide/perl.html#Exception_Handling_for_mod_perl
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://apachetoday.com http://logilune.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: Throwing die in Apache::Registry
Posted by Mark Maunder <ma...@swiftcamel.com>.
OK this is a little embarrasing... I assumed the script was die'ing when it hit the
XML::Parser routine and that eval wasn't catching the exception. Well the Apache
child is actually segfaulting. (Excuse: I'm running virtual hosts with seperate
logs. I didn't check the main error_log.). I checked the list archive and there's
tons of documentation about this and I think I saw a patch. (If anyone has more info
though, I'd appreciate it.) I'm running XML::Parser 2.30.
Thanks for the help and sorry about the time waster :)
Perrin Harkins wrote:
> on 5/4/01 9:28 AM, Mark Maunder at mark@swiftcamel.com wrote:
> > I have an Apache::Registry script that is using XML::Parser. The parser throws
> > a
> > 'die' call if it encounters a parse error (Why?).
>
> Because it's an exception and the parser can't continue.
>
> > I was handling this by
> > putting
> > the code in an eval block, but this no longer works since all Registry scripts
> > are already in one huge eval block.
>
> It should still work. An eval{} is scoped like any other block. Maybe you
> have a typo? Post your code and we'll look at it.
>
> - Perrin
--
Mark Maunder
mark@swiftcamel.com
http://swiftcamel.com/
Try not.
Do.
Or do not.
There is no try.
~yoda
Re: Throwing die in Apache::Registry
Posted by Ken Williams <ke...@forum.swarthmore.edu>.
matt@sergeant.org (Matt Sergeant) wrote:
>On Fri, 4 May 2001, Perrin Harkins wrote:
>> on 5/4/01 9:28 AM, Mark Maunder at mark@swiftcamel.com wrote:
>> > I have an Apache::Registry script that is using XML::Parser. The
>> > parser throws a 'die' call if it encounters a parse error (Why?).
>>
>> Because it's an exception and the parser can't continue.
>>
>> > I was handling this by putting the code in an eval block, but this
>> > no longer works since all Registry scripts are already in one huge
>> > eval block.
>>
>> It should still work. An eval{} is scoped like any other block. Maybe you
>> have a typo? Post your code and we'll look at it.
>
>More likely is a b0rked $SIG{__DIE__} handler, like fatalsToBrowser. Yick.
If he's throwing a die, the randomness is probably going to make it hard
to track down the problem. But there should be a 1 in 6 chance of
failure, so at least you can figure out the various distributions.
[Sorry, I'm teaching a probability class right now.]
------------------- -------------------
Ken Williams Last Bastion of Euclidity
ken@forum.swarthmore.edu The Math Forum
Re: Throwing die in Apache::Registry
Posted by Matt Sergeant <ma...@sergeant.org>.
On Fri, 4 May 2001, Perrin Harkins wrote:
> on 5/4/01 9:28 AM, Mark Maunder at mark@swiftcamel.com wrote:
> > I have an Apache::Registry script that is using XML::Parser. The parser throws
> > a
> > 'die' call if it encounters a parse error (Why?).
>
> Because it's an exception and the parser can't continue.
>
> > I was handling this by
> > putting
> > the code in an eval block, but this no longer works since all Registry scripts
> > are already in one huge eval block.
>
> It should still work. An eval{} is scoped like any other block. Maybe you
> have a typo? Post your code and we'll look at it.
More likely is a b0rked $SIG{__DIE__} handler, like fatalsToBrowser. Yick.
--
<Matt/>
/|| ** Founder and CTO ** ** http://axkit.com/ **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** mod_perl news and resources: http://take23.org **
\\//
//\\
// \\
Re: Throwing die in Apache::Registry
Posted by Perrin Harkins <pe...@elem.com>.
on 5/4/01 9:28 AM, Mark Maunder at mark@swiftcamel.com wrote:
> I have an Apache::Registry script that is using XML::Parser. The parser throws
> a
> 'die' call if it encounters a parse error (Why?).
Because it's an exception and the parser can't continue.
> I was handling this by
> putting
> the code in an eval block, but this no longer works since all Registry scripts
> are already in one huge eval block.
It should still work. An eval{} is scoped like any other block. Maybe you
have a typo? Post your code and we'll look at it.
- Perrin
Throwing die in Apache::Registry
Posted by Mark Maunder <ma...@swiftcamel.com>.
Hi,
I'm sure this has been discussed, appologies if it has, but I scoured the lists
and docs and didn't get any help.
I have an Apache::Registry script that is using XML::Parser. The parser throws a
'die' call if it encounters a parse error (Why?). I was handling this by putting
the code in an eval block, but this no longer works since all Registry scripts
are already in one huge eval block. So whenever I get a parse error, my code
ignores my eval block which encapsulates it and jumps to the end of the Registry
eval block and effectivelly exits. How does one 'eval' code that might call 'die'
under Apache::Registry?
Mark.
Re: unable to makefile of the modperl
Posted by Stas Bekman <st...@stason.org>.
Anuradha,
Please don't turn mailing lists replies into private threads. If I've
replied to the list and not privately to you, this means that I wanted the
replies and follow-ups to go to the list. We [supporting community] do
this for these reasons:
* We didn't volunteer to be your private help-desk, we reply when we can
and know, so by keeping the replies on the list we distribute the work
between us all.
* Other people might encounter the same problem, and they will benefit
from reading the replies and troubleshooting notes for the same problem.
* Finally the list is archived and people reuse the answers later on,
without bothering the list with repeated questions.
* Also very infrequently you might receive a bad advice, and you might not
be aware of it. The list dwellers will detect this (almost) immediately.
Please understand these rules and keep list replies at the list.
[ Of course if someone replies to your question in private you should keep
the reply private, don't repost it in public unless you have the other
person's permission to do that! ]
Thanks!
See some hints below:
On Fri, 4 May 2001, Anuradha Satyanarayana wrote:
>
>
>
> Thanks a lot !!!
> After all i got a reply. I am still stuck with the same problem.
> I have already installed LW P modules, HTML::HeadParser is also installed,
> Apache 1.3.4, libwwwp, and all the other modules. Still then i am getting
> these daignostic messages.
> In some mails in the mailing list, some guy had got the same problem and u
> had mentioned him to upgrade his Apache Version. Please tell me if i need
> to do so.
> I have Apache1.3.4 installed on my machine and modperl 1.25 version.
> The problem comes once i give the Makefile command.
> Perl Makefile APACHE_SRC=../../src NO_HTTPD=1 USE APACI=1 EVERYTHING=1
> I have thoroughly gone throught the documentation but could not find any
> exact answer.
> Will be waiting for your reply.
> Thanks and regards
> Anuradha
Chances are that you have a few different Perl installations and you use a
different Perl when you build mod_perl. To check this, run:
$ perl -V
look at the @INC and make sure that the reported missing modules installed
in one of the paths reported in @INC. This should resolve your problem.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: unable to makefile of the modperl
Posted by Anuradha Satyanarayana <as...@ascend.com>.
Thanks a lot !!!
After all i got a reply. I am still stuck with the same problem.
I have already installed LW P modules, HTML::HeadParser is also installed,
Apache 1.3.4, libwwwp, and all the other modules. Still then i am getting
these daignostic messages.
In some mails in the mailing list, some guy had got the same problem and u
had mentioned him to upgrade his Apache Version. Please tell me if i need
to do so.
I have Apache1.3.4 installed on my machine and modperl 1.25 version.
The problem comes once i give the Makefile command.
Perl Makefile APACHE_SRC=../../src NO_HTTPD=1 USE APACI=1 EVERYTHING=1
I have thoroughly gone throught the documentation but could not find any
exact answer.
Will be waiting for your reply.
Thanks and regards
Anuradha
Stas Bekman wrote:
> On Thu, 3 May 2001, Anuradha Satyanarayana wrote:
>
> > Unable to make the modperl Makefile.PL downloaded from perl.apache.org.
> > throwing errors like the following:
> >
> >
> > Checking for LWP::UserAgent......failed
> > Can't locate HTTP/Request.pm in @INC at lib/LWP/UserAgent.pm line 97.
> > BEGIN failed--compilation aborted at lib/LWP/UserAgent.pm line 97.
> >
> > The libwww-perl library is needed to run the test suite.
> > Installation of this library is recommended, but not required.
> >
> > Checking for HTML::HeadParser....failed
> > Can't locate HTML/HeadParser.pm in @INC at Makefile.PL line 1129.
> >
> >
> > Can anyone help?
>
> Aren't the diagnostic messages clear enough? You need to install these
> modules before you build mod_perl (at least to run 'make test')...
>
> One of the easy ways to do that:
>
> $ perl -MCPAN -eshell
> cpan> install LWP::UserAgent HTML::HeadParser
>
> Hope this helps...
>
> P.S. Make sure you read various and copious mod_perl documentation before
> it starts raining here on the list :) See http://perl.apache.org/#docs
>
> _____________________________________________________________________
> Stas Bekman JAm_pH -- Just Another mod_perl Hacker
> http://stason.org/ mod_perl Guide http://perl.apache.org/guide
> mailto:stas@stason.org http://apachetoday.com http://eXtropia.com/
> http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: unable to makefile of the modperl
Posted by Stas Bekman <st...@stason.org>.
On Thu, 3 May 2001, Anuradha Satyanarayana wrote:
> Unable to make the modperl Makefile.PL downloaded from perl.apache.org.
> throwing errors like the following:
>
>
> Checking for LWP::UserAgent......failed
> Can't locate HTTP/Request.pm in @INC at lib/LWP/UserAgent.pm line 97.
> BEGIN failed--compilation aborted at lib/LWP/UserAgent.pm line 97.
>
> The libwww-perl library is needed to run the test suite.
> Installation of this library is recommended, but not required.
>
> Checking for HTML::HeadParser....failed
> Can't locate HTML/HeadParser.pm in @INC at Makefile.PL line 1129.
>
>
> Can anyone help?
Aren't the diagnostic messages clear enough? You need to install these
modules before you build mod_perl (at least to run 'make test')...
One of the easy ways to do that:
$ perl -MCPAN -eshell
cpan> install LWP::UserAgent HTML::HeadParser
Hope this helps...
P.S. Make sure you read various and copious mod_perl documentation before
it starts raining here on the list :) See http://perl.apache.org/#docs
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/