[Lognorm] last call for next liblognorm release

Tomas Heinrich theinric at redhat.com
Tue Mar 10 13:37:27 CET 2015


On 03/10/15 09:28, Rainer Gerhards wrote:
> It's a warning, and it's not a real problem. But the detection of
> json_object_object_get_ex() does not work on el6. On other platforms,
> configure detects it, and so the old one is never used. On el6, it looks
> like it doesn't detect the function, and so the "json compatiblitly
> layer" in liblognorm is invoked, which calls the old function. A little
> bit of overhead involved, but mostly the issue is what's going on.

OK, now I think I understand better.

Here, on el6, configure actually picks it up:
checking for json_object_object_get_ex... yes

$ rpm -q json-c
json-c-0.11-11.el6.x86_64

I still get warnings about json_object_object_get() being deprecated, 
but those are from different parts of the sources:
lognormalizer.c:156: warning: ‘json_object_object_get’ is deprecated 
(declared at /usr/include/json-c/json_object.h:271)
enc_xml.c:207: warning: 'json_object_object_get' is deprecated (declared 
at /usr/include/json-c/json_object.h:271)
enc_csv.c:200: warning: 'json_object_object_get' is deprecated (declared 
at /usr/include/json-c/json_object.h:271)
enc_syslog.c:186: warning: 'json_object_object_get' is deprecated 
(declared at /usr/include/json-c/json_object.h:271)

> In any case, I'll release with more or less cosmetic issue. We can
> always "fix" it later.

Agreed.

Tomas



More information about the Lognorm mailing list