From: Andre Przywara <andre.przywara@amd.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Olaf Hering <olaf@aepfle.de>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] tools/check: check for yajl (needed by libxl)
Date: Tue, 4 Oct 2011 16:48:42 +0200 [thread overview]
Message-ID: <4E8B1CCA.4040805@amd.com> (raw)
In-Reply-To: <1317379194.26672.256.camel@zakaz.uk.xensource.com>
On 09/30/2011 12:39 PM, Ian Campbell wrote:
> On Fri, 2011-09-30 at 11:35 +0100, Anthony PERARD wrote:
>> On Fri, Sep 30, 2011 at 08:36, Ian Campbell<ian.campbell@citrix.com> wrote:
>> ...
>> You probably want to check the yajl headers as well, no ?
>> #include<yajl/yajl_parse.h>
>> #include<yajl/yajl_gen.h>
>
> tools/check seems a bit inconsistent and I'd expect them both to be in
> the -dev package but I guess it can't hurt.
>
> # HG changeset patch
> # User Ian Campbell<ian.campbell@citrix.com>
> # Date 1317379175 -3600
> # Node ID de602616358b7def9351850f518e453c68141c4f
> # Parent 302b7556edd91a7506f2215bed5302b4b5eaa52a
> tools/check: check for yajl (needed by libxl)
>
> Signed-off-by: Ian Campbell<ian.campbell@citrix.com>
> ---
> (note to committer, ensure the new files are executable)
>
> diff -r 302b7556edd9 -r de602616358b tools/check/check_yajl_devel
> --- /dev/null Thu Jan 01 00:00:00 1970 +0000
> +++ b/tools/check/check_yajl_devel Fri Sep 30 11:39:35 2011 +0100
> @@ -0,0 +1,7 @@
> +#!/bin/sh
> +# CHECK-BUILD CHECK-INSTALL
Shouldn't you be able to omit the CHECK_INSTALL on this one?
The header files are not a runtime requirement, right?
Also wouldn't it be nicer to link this small library statically? This
would omit the runtime requirement at all.
The test team just spelled yajl as "yet another library to get Xen
running"...
Also be advised that it looks like this is relying on version 1 of yajl.
It looks like the new version 2.0.1 is not compatible, I got compile
errors with the newer version. If the stable version 1.x is required,
this should be stated somewhere or at least checked properly in check_yajl.
Regards,
Andre.
> +
> +. ./funcs.sh
> +
> +has_header yajl/yajl_parse.h || fail "can't find yajl/yajl_parse.h"
> +has_header yajl/yajl_gen.h || fail "can't find yajl/yajl_gen.h"
> diff -r 302b7556edd9 -r de602616358b tools/check/check_yajl_lib
> --- /dev/null Thu Jan 01 00:00:00 1970 +0000
> +++ b/tools/check/check_yajl_lib Fri Sep 30 11:39:35 2011 +0100
> @@ -0,0 +1,6 @@
> +#!/bin/sh
> +# CHECK-BUILD CHECK-INSTALL
> +
> +. ./funcs.sh
> +
> +has_lib libyajl.so || fail "can't find libyajl.so"
>
>
next prev parent reply other threads:[~2011-10-04 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 7:36 [PATCH] tools/check: check for yajl (needed by libxl) Ian Campbell
2011-09-30 10:35 ` Anthony PERARD
2011-09-30 10:39 ` Ian Campbell
2011-10-04 14:48 ` Andre Przywara [this message]
2011-10-04 15:00 ` Ian Campbell
2011-10-05 8:24 ` Andre Przywara
2011-10-05 9:35 ` Ian Campbell
2011-10-05 11:57 ` Olaf Hering
2011-09-30 12:02 ` Olaf Hering
2011-09-30 12:07 ` Ian Campbell
2011-09-30 12:15 ` Olaf Hering
2011-09-30 12:20 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2011-10-05 9:42 Ian Campbell
2011-10-10 15:50 ` Ian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E8B1CCA.4040805@amd.com \
--to=andre.przywara@amd.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.