23 Jan
2003
23 Jan
'03
9:29 a.m.
Thanks. I've found the problem, it is in libol and was committed independently of my syslog-ng release. Here is the fix, I'll release a new libol ASAP.
Is it possible to change configure to require libol >= 0.3.8? -andrey