Displaying 20 results from an estimated 20000 matches similar to: "Asterisk 13 on CentOS 6"
2018 Nov 01
2
Jansson not found when compiling Samba
I am trying to compile Samba 4.9.1, on Ubuntu 18.04.1 server. However, when I try to configure, it says that jansson is not found. I have installed libjansson-dev from the repo (version 2.11-1), but still get the error.
Config.log says:
Checking for jansson
/bin/sh: 1: --cflags: not found
not found
2018 Aug 17
4
Re: [PATCH v3 1/4] mltools: Rename Yajl module as JSON_parser and move to common/mltools.
On 08/17/2018 10:16 AM, Richard W.M. Jones wrote:
> Commit bd1c5c9f4dcf38458099db8a0bf4659a07ef055d changed all the code
> to use Jansson instead of yajl. However it didn't change the OCaml
> API name (which was still Yajl).
>
Are you aware that Jansson can't parse all JSON generated by qemu, and
that the developers of Jansson did not seem sympathetic to patches that
would
2018 Aug 08
1
Re: LIBVIRT-4.6.0 can't work with QEMU 3.0.0
On Wed, Aug 08, 2018 at 10:06:12 +0100, Daniel Berrange wrote:
> On Wed, Aug 08, 2018 at 10:58:50AM +0200, Holger Schranz wrote:
>
> > checking for JANSSON... no
>
> This is the problem. In 4.6.0 we just switched to using JANSSOn instead
> of yajl for JSON parsing. Your host doesn't have the development headers
> installed for jansson....
>
>
> >
2018 Aug 17
1
Re: [PATCH v3 1/4] mltools: Rename Yajl module as JSON_parser and move to common/mltools.
On 08/17/2018 10:48 AM, Richard W.M. Jones wrote:
> On Fri, Aug 17, 2018 at 10:30:35AM -0500, Eric Blake wrote:
>> On 08/17/2018 10:16 AM, Richard W.M. Jones wrote:
>>> Commit bd1c5c9f4dcf38458099db8a0bf4659a07ef055d changed all the code
>>> to use Jansson instead of yajl. However it didn't change the OCaml
>>> API name (which was still Yajl).
>>>
2017 Nov 23
1
Re: [PATCH 1/1] Switch from YAJL to Jansson
On 11/23/2017 07:23 AM, Pino Toscano wrote:
> While YAJL mostly works fine, it did not see any active development in
> the latest 3 years. OTOH, Jansson is another JSON C implementation,
> with a very liberal license, and a much nicer API.
>
> Hence, switch all of libguestfs from YAJL to Jansson:
> - configure checks, and buildsystem in general
> - packages pulled in the
2017 Sep 13
4
Update to 7.4 using DVD
I am attempting to update to 7.4 using the DVD
I get these errors(truncated list)
Error: Package: libgpod-0.8.3-14.el7.x86_64 (@epel)
Requires: libusbmuxd.so.2()(64bit)
Removing: usbmuxd-1.0.8-11.el7.x86_64 (@anaconda)
libusbmuxd.so.2()(64bit)
Obsoleted By: usbmuxd-1.1.0-1.el7.x86_64 (c7-media)
Not found
Error: Package:
2018 Feb 13
1
[PATCH] build: mandate Jansson >= 2.7
Since we use APIs added in Jansson 2.7 (e.g. json_string_length), then
raise the minimum version required to that version.
Fixes commit bd1c5c9f4dcf38458099db8a0bf4659a07ef055d.
---
docs/guestfs-building.pod | 2 +-
m4/guestfs-libraries.m4 | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/guestfs-building.pod b/docs/guestfs-building.pod
index bf80984e4..db429f1a9
2018 Feb 12
2
[PATCH v2 0/1] RFC: switch from YAJL to Jansson
Hi,
recently, there was a discussion in the development list of libvirt on
switching to a different JSON library than YAJL [1]. Since we use YAJL,
and the points there IMHO apply to libguestfs as well, I decided to give
a try in switching to Jansson [2].
The result IMHO is nice, with the additional APIs of Jansson that
simplify some of our code. Unlike with YAJL, I did not set a minimum
2017 Nov 23
4
[PATCH 0/1] RFC: switch from YAJL to Jansson
Hi,
recently, there was a discussion in the development list of libvirt on
switching to a different JSON library than YAJL [1]. Since we use YAJL,
and the points there IMHO apply to libguestfs as well, I decided to give
a try in switching to Jansson [2].
The result IMHO is nice, with the additional APIs of Jansson that
simplify some of our code. Unlike with YAJL, I did not set a minimum
2017 Nov 23
1
Re: [PATCH 1/1] Switch from YAJL to Jansson
On Thu, Nov 23, 2017 at 02:23:52PM +0100, Pino Toscano wrote:
>While YAJL mostly works fine, it did not see any active development in
>the latest 3 years. OTOH, Jansson is another JSON C implementation,
>with a very liberal license, and a much nicer API.
>
>Hence, switch all of libguestfs from YAJL to Jansson:
>- configure checks, and buildsystem in general
>- packages pulled
2019 Dec 17
2
ARI strange bug on version 13.29.2
Hello,
I am using an ARI dialer for my applications and since my last upgrade
to Ver. 13.29.2 from 13.23.1 I am getting this strange bug from the ARI debugger:
Debugging on all applications enabled
<--- ARI request received from: x.x.x.x:63036 --->
HOST: x.x.x.x:8088
content-type: application/json
authorization: Basic xxxx
content-length: 265
body:
{
"context":
2018 Aug 20
1
Re: [PATCH v3 1/4] mltools: Rename Yajl module as JSON_parser and move to common/mltools.
On Friday, 17 August 2018 17:16:10 CEST Richard W.M. Jones wrote:
> Commit bd1c5c9f4dcf38458099db8a0bf4659a07ef055d changed all the code
> to use Jansson instead of yajl. However it didn't change the OCaml
> API name (which was still Yajl).
This was done initially to avoid much larger patch/series for the
yajl -> jansson conversion. And then... I forgot :-)
> -type yajl_val
2017 Apr 26
5
** in extensions.conf
I just tried this in my extensions.conf
exten => **,1,Noop(Testing)
exten => **,n,Playback(demo-congrats)
Did a reload... and the above does not happen.
I created as 12 instead of the ** and that works fine.
Is there anyway to get the ** to work? I also am using a polycom phone if
that affects things. I'm using asterisk 13.15.0
Thanks
Jerry
-------------- next part --------------
2018 Aug 08
3
Re: LIBVIRT-4.6.0 can't work with QEMU 3.0.0
2018 Aug 17
8
[PATCH v3 4/4] v2v: Add --print-estimate option to print copy size
I rethought this again, as I think that it's a dangerous assumption to
bake qemu-img measure output into our API.
This patch series runs qemu-img measure behind the scenes, but then
parses the output and sums it to a single number which we print.
Doing that required a bit of reworking, moving the Jansson [JSON
parser] bindings from virt-builder into the common directory and
a couple of other
2020 Jul 22
1
回复: 回复: bug report
Hi,Richard:
I use /bin/virt-copy-in failed , virt-copy-in have no diff with other nomarl machine(work well ) ,
/bin/virt-copy-in: symbol lookup error: /lib64/libguestfs.so.0: undefined symbol: json_string_length
here are
2017 Nov 23
0
[PATCH 1/1] Switch from YAJL to Jansson
While YAJL mostly works fine, it did not see any active development in
the latest 3 years. OTOH, Jansson is another JSON C implementation,
with a very liberal license, and a much nicer API.
Hence, switch all of libguestfs from YAJL to Jansson:
- configure checks, and buildsystem in general
- packages pulled in the appliance
- actual implementations
- contrib scripts
- documentation
This also
2018 Feb 12
0
[PATCH v2 1/1] Switch from YAJL to Jansson
While YAJL mostly works fine, it did not see any active development in
the last 3 years. OTOH, Jansson is another JSON C implementation, with
a very liberal license, and a much nicer API.
Hence, switch all of libguestfs from YAJL to Jansson:
- configure checks, and buildsystem in general
- packages pulled in the appliance
- actual implementations
- contrib scripts
- documentation
This also
2013 Oct 21
3
Asterisk-12 issue after successful installation
Hi Team,
I have installed asterisk-12 Beta but when I try to asterisk start then get
below issue.
*[root at cs-gb-pwr-1-04 asterisk-12.0.0-beta1]# asterisk -r
asterisk: error while loading shared libraries: libjansson.so.4: cannot
open shared object file: No such file or directory
[root at cs-gb-pwr-1-04 asterisk-12.0.0-beta1]#*
--
Thanks and regards
Virendra Bhati
+91-9718500594
2018 Aug 17
0
Re: [PATCH v3 1/4] mltools: Rename Yajl module as JSON_parser and move to common/mltools.
On Friday, 17 August 2018 17:30:35 CEST Eric Blake wrote:
> On 08/17/2018 10:16 AM, Richard W.M. Jones wrote:
> > Commit bd1c5c9f4dcf38458099db8a0bf4659a07ef055d changed all the code
> > to use Jansson instead of yajl. However it didn't change the OCaml
> > API name (which was still Yajl).
> >
>
> Are you aware that Jansson can't parse all JSON generated