At 04:58 AM 8/13/2004, NormW wrote:
>Good evening Bill, All...
>
>> Please direct these comments to [EMAIL PROTECTED] - b.t.w., you
>> can check out the latest httpd-2.0 HEAD and pick up the entire proxy
>> solution (you must explicitly --enable-proxy-ajp and have the ajplib
>> sources there too.)
>>
>> Someone want to take a wack at NormW's observations?
>Bill, thanks for the interest...
>I can say that the 'problem' noted in proxy_ftp.c has been attended with a
>recent update from Mladen.
>A build on the current 2.1 CVS shows (for NetWare):
>- mod_proxy.c having trouble finding mod_status.h   (in
>../modules/generators),
>- the same problem mentioned previously with proxy_connect.c, (Errors at 375
>see 26, 80)
>Bypassing these I now get:
>Calling NWGNUproxyftp
>Generating Release\proxyftp_cc.opt
>Compiling proxy_ftp.c
>Compiling proxy_util.c
>Compiling ../arch/netware/libprews.c
>Generating Release\proxyftp_link.opt
>Linking Release/proxyftp.nlm
>### mwldnlm Linker Error:
>#   Undefined symbol: 'ap_proxy_ssl_enable'
>#   referenced from 'ap_proxy_connection_create' in proxy_util.o
>### mwldnlm Linker Error:
>#   Undefined symbol: 'ap_proxy_ssl_disable'
>#   referenced from 'ap_proxy_connection_create' in proxy_util.o
>
>As noted above, this is on a NetWare build...

It's expected because the netware gurus haven't had a chance to
catch up.  Please quit using tomcat-dev already - final warning;
ignoring future posts to there in order to enforce posting future
proxy patches/comments to [EMAIL PROTECTED] ;-)

I suspect Netware didn't grok that those symbols were local/global
as required?

Bill


Reply via email to