>=20 > 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. >=20 Is it possible to change configure to require libol >=3D 0.3.8? -andrey