23 Jan
2003
23 Jan
'03
10:38 a.m.
On Thu, Jan 23, 2003 at 12:29:12PM +0300, Borzenkov Andrey wrote:
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?
I've changed my configure script in CVS to require libol 0.3.8. I've also updated the webpage so it says syslog-ng 1.5.25 requires 0.3.8, hopefully nobody else runs into this problem. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1