Hi,
I'm trying to back-port Apache Module mod_proxy_fdpass to httpd-2.2.19,
and building from source, but are getting the following error message
when starting apachectl:
httpd: Module "(null)" is not compatible with this version of Apache
(found 0, need 20051115). Please contact the vendor for t
> From: Henrik Strand [mailto:[email protected]]
> Sent: Wednesday, 3 August 2011 5:10 PM
> To: [email protected]
> Subject: mod_proxy_fdpass + httpd-2.2.19
>
> Hi,
>
> I'm trying to back-port Apache Module mod_proxy_fdpass to httpd-2.2.19,
> and building from source, but are gett
On 3 Aug 2011, at 08:10, Henrik Strand wrote:
> Hi,
>
> I'm trying to back-port Apache Module mod_proxy_fdpass to httpd-2.2.19,
> and building from source, but are getting the following error message
> when starting apachectl:
>
> httpd: Module "(null)" is not compatible with this version of Ap
Hi Nick,
Yes, that's right.
// AP_DECLARE_MODULE(proxy_fdpass) = {
module AP_MODULE_DECLARE_DATA proxy_fdpass = {
STANDARD20_MODULE_STUFF,
NULL, /* create per-directory config structure
*/
NULL, /* merge per-directory config structures
*/
On 3 Aug 2011, at 09:27, Henrik Strand wrote:
> module AP_MODULE_DECLARE_DATA proxy_fdpass = {
>STANDARD20_MODULE_STUFF,
>NULL, /* create per-directory config structure
> */
>NULL, /* merge per-directory config structures
> */
>NULL,
Hmm, but this is how the code looks like when I get the error that I
posted.
Is the module initialization done with the below code, or do I need to
add that explicitly?
Best Regards,
Henrik
On Wed, 2011-08-03 at 10:41 +0200, Nick Kew wrote:
> On 3 Aug 2011, at 09:27, Henrik Strand wrote:
>
> >
On 03.08.2011 09:48, Tony Abo wrote:
>> From: Henrik Strand [mailto:[email protected]]
>> Sent: Wednesday, 3 August 2011 5:10 PM
>> To: [email protected]
>> Subject: mod_proxy_fdpass + httpd-2.2.19
>>
>> Hi,
>>
>> I'm trying to back-port Apache Module mod_proxy_fdpass to httpd-2.2.1
On 3 Aug 2011, at 10:26, Henrik Strand wrote:
> Hmm, but this is how the code looks like when I get the error that I
> posted.
In that case, you've compiled it against the wrong headers.
The best solution is usually to use apxs from the installed version
to compile new modules.
That error mess
