<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
I already created a ticket :)<br>
<br>
<br>
On 06/23/2014 10:57 AM, Rainer Gerhards wrote:<br>
<span style="white-space: pre;">><br>
> Is it ok if i post this to the github ticket?<br>
><br>
> Sent from phone, thus brief.<br>
><br>
> Am 23.06.2014 16:18 schrieb "Champ Clark III"
<<a class="moz-txt-link-abbreviated" href="mailto:cclark@quadrantsec.com">cclark@quadrantsec.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:cclark@quadrantsec.com"><mailto:cclark@quadrantsec.com></a>>:<br>
><br>
><br>
> > This looks to me like it is from the header file, not
configure.ac <a class="moz-txt-link-rfc2396E" href="http://configure.ac"><http://configure.ac></a>
<a class="moz-txt-link-rfc2396E" href="http://configure.ac"><http://configure.ac></a> <a class="moz-txt-link-rfc2396E" href="http://configure.ac"><http://configure.ac></a>. 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...<br>
><br>
> > In any case, I think opening a github tracker would
probably be best, as volume on the lognorm list is unfortunately
rather limited.<br>
><br>
> > Rainer<br>
><br>
> The problem is the liblognorm.h (header) file, no the
configure.ac <a class="moz-txt-link-rfc2396E" href="http://configure.ac"><http://configure.ac></a>. The paths that "are not
correctly setup" or what the distributions supply. That is, an
"apt-get install libjson0 libjson-dev" result in the json.h being
in the /usr/include/json directory. What I was suggesting is
that the configure.ac <a class="moz-txt-link-rfc2396E" href="http://configure.ac"><http://configure.ac></a> be made to test
the path of the json.h file. That way, liblognorm can "adjust"
to if the json.h is in the /usr/include or the /usr/include/json
directories.<br>
><br>
> I'm opening a ticket on Github now.<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Lognorm mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Lognorm@lists.adiscon.com">Lognorm@lists.adiscon.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:Lognorm@lists.adiscon.com"><mailto:Lognorm@lists.adiscon.com></a><br>
> <a class="moz-txt-link-freetext" href="http://lists.adiscon.net/mailman/listinfo/lognorm">http://lists.adiscon.net/mailman/listinfo/lognorm</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Lognorm mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Lognorm@lists.adiscon.com">Lognorm@lists.adiscon.com</a><br>
> <a class="moz-txt-link-freetext" href="http://lists.adiscon.net/mailman/listinfo/lognorm">http://lists.adiscon.net/mailman/listinfo/lognorm</a></span><br>
<br>
- -- <br>
- - Quadrant Information Security<br>
Champ Clark III<br>
o: 800.538.9357 x 101<br>
c: 850.443.2440<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.11 (GNU/Linux)<br>
Comment: Using GnuPG with Thunderbird - <a class="moz-txt-link-freetext" href="http://www.enigmail.net/">http://www.enigmail.net/</a><br>
<br>
iQEcBAEBAgAGBQJTqEDiAAoJENnmXt7Lmc3KOFIH/AhenyrhkU9+UaTAh+uWupP3<br>
2P8p4bJNC4lWo3acZv9jfSAzyFLG3d8AAhVN1bzo6IxKaFA3MCSg1G8yZaGb7NMa<br>
zbX8iqbAtUdKaoCKPln4p+xkFMpFs5yAa3Rp8QKLCQ+7qMUA4oV3lrTCmOrqJSdK<br>
BChNpkD5G1/9Ico/Q6vacI4F9VFZxNIKHJZmePTiPS46wGeA3Cbix12g6leIZaGa<br>
MBKE2k4vsCc0+HIRr8uxaKwF+EXiU+6lORo8nK+YohAMbVLB3CMiXwfe/poWX3Y6<br>
5ltoyd8VjX4+I+I9LGsC1hfyHvRzVfzmuAj2DftEAo6nVuqFkwzOpQacTRJlax8=<br>
=SnoT<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>