[Lognorm] json.h: No such file or directory

[Rainer Gerhards]

On Mon, Jun 23, 2014 at 6:20 AM, Champ Clark III <cclark at quadrantsec.com>
wrote:

> Hello all.....
>
> I brought this issue up some time ago and thought I would bring it up
> again.
>
> In the liblognorm.h,  the json.h is hard coded as "#include <json.h>".
> In some Linux distributions,  the json-c headers ends up in #include
> <json/json.h>.
>
> This issue comes up when attempting to link applications with
> liblognorm.  For example,  I have pulled and installed libestr and
> liblognorm from Github a few minutes
> ago.   This is a brand new Ubuntu 12.04 box.
>
> When I go to compile Sagan with liblognorm support (which is default),
> I get the following error:
>
> --<snip>--
>
> In file included from sagan-config.c:49:0:
> /usr/local/include/liblognorm.h:64:18: fatal error: json.h: No such file
> or directory
> compilation terminated.
> make[2]: *** [sagan-config.o] Error 1
>
> --<snip>--
>
> In order to fix this issue,  I have to manually edit the
> /usr/local/include/liblognorm.h file and change:
>
> #include <json.h>
>
> to
>
> # include <json/json.h>
>
> I had a similar problem with Sagan and addressed it this way.  In my
> configure.ac i have the following:
>
> --<snip>--
>
> #if defined(HAVE_JSON_JSON_H)
> #  include <json/json.h>
> #else
> #  include <json.h>
> #endif
>
> --<snip>--
>
>
This looks to me like it is from the header file, not configure.ac. Is it?
In essence, I think we would need to *build* the header file according to
the installed version. I think when this came up, someone (Pavel?) said
that this error just comes up when the json-c search pathes are not
correctly set up ... or so...

In any case, I think opening a github tracker would probably be best, as
volume on the lognorm list is unfortunately rather limited.

Rainer


> Right now,  when this issue comes up,  I have to tell people to manually
> edit the liblognorm.h file and manually change the json.h locations .
> I've experienced this
> problem with Ubuntu and Gentoo. The issue has been reported on Fedora
> Core 19.
>
>
> https://groups.google.com/forum/#!msg/sagan-users/o9vBF2CAq_g/9ZWIiejoFwcJ
>
> Let me know your thoughts and thank you!
>
>
>
> _______________________________________________
> Lognorm mailing list
> Lognorm at lists.adiscon.com
> http://lists.adiscon.net/mailman/listinfo/lognorm
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.adiscon.net/pipermail/lognorm/attachments/20140623/976214ba/attachment.html>