Re: MP and 2.4 Compilation Woes

"Kevin A. McGrail" <[email protected]>
Newsgroups gmane.comp.apache.mod-perl
Message-ID <[email protected]>
On 2/8/2013 10:48 AM, Andy Colson wrote:
> On 2/8/2013 9:39 AM, Kevin A. McGrail wrote:
>> Hi All,
>>
>> So picking back up on the thread from the httpd list, I am interested in
>> helping with mod_perl.  And I've written some patches for AuthenDBI and
>> can work on those again as well.
>>
>> However, at the moment I can't compile 2.4 and the make source_scan
>> stuff is not something I even understand nor can I find much documented
>> about it.
>>
>> I've worked through Jan's patches downloaded 9/25 and the info on
>> http://qteajs.org/howto/apache?_size=1920x1086 looked promising.
>>
>> And even though I'm also using my own custom built perl 5.14 instead of
>> the RH/CentOS builds I've tried so far, I've had no luck.
>>
>> Following Jan's advice, I had to add this to ParseSource.pm
>>
>> +     'APACHE_HTTP_VHOST_H', #c-scan chokes on http_host.h
>> +     'H_PERL', #""
>>
>> That got me this far...
>>
>> /usr/local/perl-5.14/bin/perl build/source_scan.pl
>> Expecting parenth after identifier in `const XML_Memory_Handling_Suite
>> *memsuite'
>> after `const XML_Memory_Handling_Suite ' at lib/ModPerl/CScan.pm line 
>> 895.
>> make: *** [source_scan] Error 255
>>
>> Overall, I think the concept that things should be forked to a new 2.4
>> mod_perl is best because if it's backwards compatibility that's holding
>> things back, I'd rather lose that.  I'm currently building on a devel
>> box running on CentOS 6.2.
>>
>> Regards,
>> KAM
>
>
> > /usr/local/perl-5.14/bin/perl build/source_scan.pl
>
> Have you tried:
>
> make source_scan
Yes.  That info above is the output from the end of make source_scan 
with Jan's patches, the extra patch I did similar to the 0027 patch of 
his and I think some minor patches from the qteajs.  I am stuck at this 
step.

> make xs_generate
>
> -Andy
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.