[Lognorm] Minor issue with liblognorm 1.0.0 release.

Pavel Levshin pavel at levshin.spb.ru
Tue Dec 3 06:23:53 CET 2013


02.12.2013 23:52, Champ Clark III:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Just started working with Sagan and liblognorm 1.0.0.  I've cleaned my
> dev box off all old versions of libee, libestr and liblognorm.   Then
> rebuilt from git using my normal process.
>
> It appears that liblognorm.h is trying to call:
>
> #include <json.h>
>
> My json-c is located in the /usr/include/json/json.h
>
> Easy fix manually,  but just thought you might want to know.
>
>

Thank you for the report. The header's location has changed in json-c 
0.11. Using exact path in #include would lead to complex conditional 
directives each time this header is needed.

Liblognorm makes use of pkg_config to find json-c package. There should 
be something like this in the system (this example is from RHEL6):

$ cat /usr/lib64/pkgconfig/json.pc

prefix=/usr
exec_prefix=/usr
libdir=/usr/lib64
includedir=/usr/include

Name: json
Description: JSON implementation in C
Version: 0.10
Requires:
Libs:  -L${libdir} -ljson
Cflags: -I${includedir}/json


Cflags are used to find correct header's path.


--
Pavel Levshin



More information about the Lognorm mailing list