From cclark at quadrantsec.com  Mon Jun 23 06:20:34 2014
From: cclark at quadrantsec.com (Champ Clark III)
Date: Mon, 23 Jun 2014 00:20:34 -0400
Subject: [Lognorm] json.h: No such file or directory
Message-ID: <53A7AB12.40703@quadrantsec.com>

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>--

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! 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 601 bytes
Desc: OpenPGP digital signature
URL: <http://lists.adiscon.net/pipermail/lognorm/attachments/20140623/383cab90/attachment.pgp>

From rgerhards at hq.adiscon.com  Mon Jun 23 12:49:50 2014
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Mon, 23 Jun 2014 12:49:50 +0200
Subject: [Lognorm] json.h: No such file or directory
In-Reply-To: <53A7AB12.40703@quadrantsec.com>
References: <53A7AB12.40703@quadrantsec.com>
Message-ID: <CADk+mPD+k8Yy49T-GF6NLt5xPQn=EYh0sBUh1hnOXzxPB0zEQQ@mail.gmail.com>

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>

From cclark at quadrantsec.com  Mon Jun 23 16:18:36 2014
From: cclark at quadrantsec.com (Champ Clark III)
Date: Mon, 23 Jun 2014 10:18:36 -0400
Subject: [Lognorm] json.h: No such file or directory
In-Reply-To: <CADk+mPD+k8Yy49T-GF6NLt5xPQn=EYh0sBUh1hnOXzxPB0zEQQ@mail.gmail.com>
References: <53A7AB12.40703@quadrantsec.com>
	<CADk+mPD+k8Yy49T-GF6NLt5xPQn=EYh0sBUh1hnOXzxPB0zEQQ@mail.gmail.com>
Message-ID: <53A8373C.1010307@quadrantsec.com>


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

> This looks to me like it is from the header file, not configure.ac <http://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

The problem is the liblognorm.h (header) file,  no the configure.ac. 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 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.

I'm opening a ticket on Github now.


- -- 
- - 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/

iQEcBAEBAgAGBQJTqDc8AAoJENnmXt7Lmc3Kf84H/iSxbkl+WqcdPxXLTXC1UGX9
3YBpMnLV54KgSObDT7vvhWeLtVrvFCH4BxVJ1d9ssNBkgnhZthKdDaveaHQRzWkS
ThMTIRrehSqyfaD3oxg1Jn654/oNABzsRDJi2CBQv36G4TfP+y2T4PrJrtjx3mMd
3k45ReRwEQETwmB+5lkkv97r9ptLeH4Q0bx+M3QhuHQOTVYCrR4yDFIvhv86L6qy
ni7CNtD8xv2F8tRv4EEq+ZQY3UPunKwNEUbzrj51c8/kmKEAkJ6gtohbNe+USFgA
8EgDmn+938g8R33Q2keauqV+L/EkRqZ5UQdRAZGrNVPcD029ioMYvGIJqAYLeQA=
=FxJn
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.adiscon.net/pipermail/lognorm/attachments/20140623/20c5e6f3/attachment-0001.html>

From rgerhards at hq.adiscon.com  Mon Jun 23 16:57:15 2014
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Mon, 23 Jun 2014 16:57:15 +0200
Subject: [Lognorm] json.h: No such file or directory
In-Reply-To: <53A8373C.1010307@quadrantsec.com>
References: <53A7AB12.40703@quadrantsec.com>
	<CADk+mPD+k8Yy49T-GF6NLt5xPQn=EYh0sBUh1hnOXzxPB0zEQQ@mail.gmail.com>
	<53A8373C.1010307@quadrantsec.com>
Message-ID: <CADk+mPCEd9giwQjZZALgYZtiLp0GFA7j9tLbsDWAz9Qc7nabGA@mail.gmail.com>

Is it ok if i post this to the github ticket?

Sent from phone, thus brief.
Am 23.06.2014 16:18 schrieb "Champ Clark III" <cclark at quadrantsec.com>:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > This looks to me like it is from the header file, not configure.ac
> <http://configure.ac> <http://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
>
> The problem is the liblognorm.h (header) file,  no the configure.ac. 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 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.
>
> I'm opening a ticket on Github now.
>
>
> - --
> - - 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/
>
> iQEcBAEBAgAGBQJTqDc8AAoJENnmXt7Lmc3Kf84H/iSxbkl+WqcdPxXLTXC1UGX9
> 3YBpMnLV54KgSObDT7vvhWeLtVrvFCH4BxVJ1d9ssNBkgnhZthKdDaveaHQRzWkS
> ThMTIRrehSqyfaD3oxg1Jn654/oNABzsRDJi2CBQv36G4TfP+y2T4PrJrtjx3mMd
> 3k45ReRwEQETwmB+5lkkv97r9ptLeH4Q0bx+M3QhuHQOTVYCrR4yDFIvhv86L6qy
> ni7CNtD8xv2F8tRv4EEq+ZQY3UPunKwNEUbzrj51c8/kmKEAkJ6gtohbNe+USFgA
> 8EgDmn+938g8R33Q2keauqV+L/EkRqZ5UQdRAZGrNVPcD029ioMYvGIJqAYLeQA=
> =FxJn
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> 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/52cd9e0e/attachment.html>

From cclark at quadrantsec.com  Mon Jun 23 16:59:46 2014
From: cclark at quadrantsec.com (Champ Clark III)
Date: Mon, 23 Jun 2014 10:59:46 -0400
Subject: [Lognorm] json.h: No such file or directory
In-Reply-To: <CADk+mPCEd9giwQjZZALgYZtiLp0GFA7j9tLbsDWAz9Qc7nabGA@mail.gmail.com>
References: <53A7AB12.40703@quadrantsec.com>	<CADk+mPD+k8Yy49T-GF6NLt5xPQn=EYh0sBUh1hnOXzxPB0zEQQ@mail.gmail.com>	<53A8373C.1010307@quadrantsec.com>
	<CADk+mPCEd9giwQjZZALgYZtiLp0GFA7j9tLbsDWAz9Qc7nabGA@mail.gmail.com>
Message-ID: <53A840E2.7050902@quadrantsec.com>


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

I already created a ticket :)


On 06/23/2014 10:57 AM, Rainer Gerhards wrote:
>
> Is it ok if i post this to the github ticket?
>
> Sent from phone, thus brief.
>
> Am 23.06.2014 16:18 schrieb "Champ Clark III" <cclark at quadrantsec.com
<mailto:cclark at quadrantsec.com>>:
>
>
> > This looks to me like it is from the header file, not configure.ac
<http://configure.ac> <http://configure.ac> <http://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
>
> The problem is the liblognorm.h (header) file,  no the configure.ac
<http://configure.ac>. 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
<http://configure.ac> 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.
>
> I'm opening a ticket on Github now.
>
>
>
>
>     _______________________________________________
>     Lognorm mailing list
>     Lognorm at lists.adiscon.com <mailto:Lognorm at lists.adiscon.com>
>     http://lists.adiscon.net/mailman/listinfo/lognorm
>
>
>
> _______________________________________________
> Lognorm mailing list
> Lognorm at lists.adiscon.com
> http://lists.adiscon.net/mailman/listinfo/lognorm

- -- 
- - 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/

iQEcBAEBAgAGBQJTqEDiAAoJENnmXt7Lmc3KOFIH/AhenyrhkU9+UaTAh+uWupP3
2P8p4bJNC4lWo3acZv9jfSAzyFLG3d8AAhVN1bzo6IxKaFA3MCSg1G8yZaGb7NMa
zbX8iqbAtUdKaoCKPln4p+xkFMpFs5yAa3Rp8QKLCQ+7qMUA4oV3lrTCmOrqJSdK
BChNpkD5G1/9Ico/Q6vacI4F9VFZxNIKHJZmePTiPS46wGeA3Cbix12g6leIZaGa
MBKE2k4vsCc0+HIRr8uxaKwF+EXiU+6lORo8nK+YohAMbVLB3CMiXwfe/poWX3Y6
5ltoyd8VjX4+I+I9LGsC1hfyHvRzVfzmuAj2DftEAo6nVuqFkwzOpQacTRJlax8=
=SnoT
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.adiscon.net/pipermail/lognorm/attachments/20140623/5f878b8e/attachment.html>

From rgerhards at hq.adiscon.com  Mon Jun 23 17:02:38 2014
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Mon, 23 Jun 2014 17:02:38 +0200
Subject: [Lognorm] json.h: No such file or directory
In-Reply-To: <53A840E2.7050902@quadrantsec.com>
References: <53A7AB12.40703@quadrantsec.com>
	<CADk+mPD+k8Yy49T-GF6NLt5xPQn=EYh0sBUh1hnOXzxPB0zEQQ@mail.gmail.com>
	<53A8373C.1010307@quadrantsec.com>
	<CADk+mPCEd9giwQjZZALgYZtiLp0GFA7j9tLbsDWAz9Qc7nabGA@mail.gmail.com>
	<53A840E2.7050902@quadrantsec.com>
Message-ID: <CADk+mPDSW90pT7vR+t_wR1OvH6++AAdeDz5zWnYxy0PZHD-Shw@mail.gmail.com>

Sent from phone, thus brief.
Am 23.06.2014 16:59 schrieb "Champ Clark III" <cclark at quadrantsec.com>:
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I already created a ticket :)

Yeah but it misses the important point you made ;) anyways I'll link to the
ML archive with my reply :)
>
>
>
> On 06/23/2014 10:57 AM, Rainer Gerhards wrote:
> >
> > Is it ok if i post this to the github ticket?
> >
> > Sent from phone, thus brief.
> >
> > Am 23.06.2014 16:18 schrieb "Champ Clark III" <cclark at quadrantsec.com
<mailto:cclark at quadrantsec.com>>:
> >
> >
> > > This looks to me like it is from the header file, not configure.ac <
http://configure.ac> <http://configure.ac> <http://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
> >
> > The problem is the liblognorm.h (header) file,  no the configure.ac <
http://configure.ac>. 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 <
http://configure.ac> 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.
>
> >
> > I'm opening a ticket on Github now.
> >
> >
> >
> >
> >     _______________________________________________
> >     Lognorm mailing list
> >     Lognorm at lists.adiscon.com <mailto:Lognorm at lists.adiscon.com>
> >     http://lists.adiscon.net/mailman/listinfo/lognorm
>
> >
> >
> >
> > _______________________________________________
> > Lognorm mailing list
> > Lognorm at lists.adiscon.com
> > http://lists.adiscon.net/mailman/listinfo/lognorm
>
>
> - --
> - - 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/
>
> iQEcBAEBAgAGBQJTqEDiAAoJENnmXt7Lmc3KOFIH/AhenyrhkU9+UaTAh+uWupP3
> 2P8p4bJNC4lWo3acZv9jfSAzyFLG3d8AAhVN1bzo6IxKaFA3MCSg1G8yZaGb7NMa
> zbX8iqbAtUdKaoCKPln4p+xkFMpFs5yAa3Rp8QKLCQ+7qMUA4oV3lrTCmOrqJSdK
> BChNpkD5G1/9Ico/Q6vacI4F9VFZxNIKHJZmePTiPS46wGeA3Cbix12g6leIZaGa
> MBKE2k4vsCc0+HIRr8uxaKwF+EXiU+6lORo8nK+YohAMbVLB3CMiXwfe/poWX3Y6
> 5ltoyd8VjX4+I+I9LGsC1hfyHvRzVfzmuAj2DftEAo6nVuqFkwzOpQacTRJlax8=
> =SnoT
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> 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/cb63761d/attachment.html>