Re: Module Compilation Changes between 2.0 and 2.2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

On Tue, Jul 27, 2010 at 02:39:32PM +0100, Nick Kew wrote:
> On Tue, 27 Jul 2010 08:03:57 -0400
> Michael Powe <michael@xxxxxxxxxxxx> wrote:
> 
> > Hello,
> > 
> > I have a module that compiles and installs for Apache httpd 2.0.47 and
> > Apache httpd 2.0.63.  However, when I try to compile for 2.2.15, I get
> > the following result:
 
> Have you asked the module author?  Someone who can write a module for 2.0
> should have no trouble updating it.

Hmm, well ... the author is a former employee of our company that left
on bad terms.  He doesn't take our calls.  I inherited this module and
I am now its maintainer.  (My first action upon receiving this good
news was to order your modules book 2nd-day air.)

So it has been a steep learning curve.  I added some functionality to
the module and the client is having issues compiling it on the staging
server. I'm certain that this is caused by trying to use 2.2 tools and
headers to compile it.  

> > I am thinking that the first error ('expected specifier-qualifier-list before
> > regex_t') may be causing a cascade effect.
> 
> ap_regex_t.  Or see the #defines at the top of mod_proxy_html for a version
> that'll compile on both 2.0 and 2.2.

Okay, thanks.  I wondered when I first went through the module code
why the author didn't use ap_regex_t.  More research is needed, I
guess. 

> The apr_socket is not a cascade: it's because httpd-2.0 uses APR 0.9.
> You'll need to fix that up yourself.

I diff'ed the two apr_network_io.h files files earlier and took a
quick look at the changes.  Working that out in my module is likely to
take a bit of work. But, the production deployment is in IBMIHS 6.1
and Apache 2.0.63; it's a corporate environment which is unlikely to
change in the foreseeable future.

Meanwhile, I need to get a clear understanding of what is happening.
Even though the APR version is a long-term block, I can deal with the
short-term issue of the regex_t error.  I've seen some commentary that
indicates it may be the result of the includes not being processed in
the correct order in relationship to the order of declarations in my
header file.  But it's sketchy.

Thanks for the reply.  And BTW, your book saved me from the
exploding-head syndrome when I got down to work on this project.
Thanks for that, too.  ;-)

mp

-- 
Michael Powe		michael@xxxxxxxxxxxx		Naugatuck CT USA
"It stands to reason that self-righteous, inflexible, single-minded,
authoritarian true believers are politically organized. Open-minded,
flexible, complex, ambiguous, anti-authoritarian people would just as
soon be left to mind their own fucking business." - R.U. Sirius

Attachment: pgpBrXnXZuljr.pgp
Description: PGP signature


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux