[Lognorm] Minor issue with liblognorm 1.0.0 release.

[Champ Clark III]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I understand.   I was just tested building liblognorm on Ubuntu 12.04.  
I have the stock package from Ubuntu for json-c.

The error is:

gcc -DHAVE_CONFIG_H -I. -I..     -g -O2 -MT sagan-config.o -MD -MP -MF
.deps/sagan-config.Tpo -c -o sagan-config.o sagan-config.c
In file included from sagan-config.c:49:0:
/usr/include/liblognorm.h:64:18: fatal error: json.h: No such file or
directory

In the /usr/include/liblognorm.h,  the location for json.h is hardcoded to:

#include <json.h>

The easy fix is to manually change this to:

#include <json/json.h>

I'm assuming that different distro's put the json.h in /usr/include or
/usr/include/json.   To get around this in Sagan,  I did this:

#if defined(HAVE_JSON_JSON_H)
#  include <json/json.h>
#else
#  include <json.h>
#endif

I've seen this minor build issue on Gentoo, Fedora and Ubuntu.




On 12/07/2013 04:51 AM, Pavel Levshin wrote:
> Hello,
>
> Could you please explain, why pkg_config does not work well in your
case? It should set correct -I option and find the header automagically.
Unless json.pc (pkg_config description file) is incorrect on
distribution you are using.
>
> Anyway, your solution will probably break with next release of json-c:
>
> 0.11
>   * IMPORTANT: the name of the library has changed to libjson-c.so and
>      the header files are now in include/json-c.
>      The pkgconfig name has also changed from json to json-c.
>      You should change your build to use appropriate -I and -l options.
>      A compatibility shim is in place so builds using the old name will
>      continue to work, but that will be removed in the next release.
>


- -- 
- - Quadrant Information Security
  Champ Clark III
  o: 800.538.9357 x 101
  c: 850.443.2440
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSpgJ9AAoJENnmXt7Lmc3KHb4H/2jZHIDmqfo3X7Q5xxxAhjZS
IK+wlmzCBR2dnq09HXckwSXzK5vNOvf+Zl46096VG8Vivbw+KslTzYyiiF9ytZpR
O8+8jxWmweLO5oMMpexhw63zJeApqPikgDg22jCJqtqFrMd3JlUQK2a3r7g9a0tb
p9u0ca+sm7+LWdo+anpQ9WbgLceugrDLqIShldCxQDvYtTmJ7QnyOAQEwXJWAGAm
VYOffwJ+Jmq/cyealeRlx8QkER2hl8sSEKij7j8jHvzHI5ff4wudiIDFL8wd1JNU
wJR6mTGt5VORu++4toXHYwWuATnGQWi7Fo3kvcVXgm+5YcqU2QTK2BrjJFJHm+g=
=imOc
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.adiscon.net/pipermail/lognorm/attachments/20131209/74b3eb70/attachment-0001.html>