ajp13 broken in last svn update

With svn version 1952, on Unbuntu feisty, when I laucnh
lighttpd, I've
got this error :

(plugin.c.266) dlopen() failed for:
/opt/lighty/lib/mod_proxy_backend_ajp13.so
/opt/lighty/lib/mod_proxy_backend_ajp13.so: undefined
symbol: ltostr

It seems to be a violent code cleaning like suggest
Changelog infos.

M.

> With svn version 1952, on Unbuntu feisty, when I laucnh
lighttpd, I've
> got this error :
> 
> (plugin.c.266) dlopen() failed for:
> /opt/lighty/lib/mod_proxy_backend_ajp13.so
> /opt/lighty/lib/mod_proxy_backend_ajp13.so: undefined
symbol: ltostr
> 
> It seems to be a violent code cleaning like suggest
Changelog infos.
Yep, the last commit from jan was 'renamed ltostr() to
LI_ltostr()'.
Apparently a lot of occurances of this function call were
not updated
and as such at least mod_proxy_backend_{ajp13,fastcgi} are
broken.
Try if sed -e 's:ltostr:LI_ltostr:g' fixes it.

Christian Hoffmann wrote:
>> With svn version 1952, on Unbuntu feisty, when I
laucnh lighttpd, I've
>> got this error :
>>
>> (plugin.c.266) dlopen() failed for:
>> /opt/lighty/lib/mod_proxy_backend_ajp13.so
>> /opt/lighty/lib/mod_proxy_backend_ajp13.so:
undefined symbol: ltostr
>>
>> It seems to be a violent code cleaning like suggest
Changelog infos.
> Yep, the last commit from jan was 'renamed ltostr() to
LI_ltostr()'.
> Apparently a lot of occurances of this function call
were not updated
> and as such at least mod_proxy_backend_{ajp13,fastcgi}
are broken.
> Try if sed -e 's:ltostr:LI_ltostr:g' fixes it.

Yep, fixed now.

cheers,
  Jan
-- 
 jan: "Gee, Brain^WEric, what'd you wanna do
tonight?"
eric: Same thing we do everynight: Take over the
HelloWorld!