Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: Chris <cheart0@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] swupdate suricatta build error
Date: Sat, 29 Jan 2022 20:07:55 +0100	[thread overview]
Message-ID: <20220129200755.17188a26@gmx.net> (raw)
In-Reply-To: <CAA6F-SOWP+gotpC8jtANa8-GZRu7ZvwcQuEMH_uNc54Yb0ibPQ@mail.gmail.com>

Hello Chris,

On Fri, 28 Jan 2022 12:59:23 +0900, Chris <cheart0@gmail.com> wrote:

> Hi, there
> Did anybody ever see the same issue? When build 2021.11 for raspberry pi,
> we added swupdate package and enabled suricatta mode by "make
> swupdate-menuconfig", then we got error as below,
> 
> suricatta/common.c:79:26: error: storage size of ‘json_res’ isn’t known
>    79 |  enum json_tokener_error json_res;
>       |                          ^~~~~~~~
> suricatta/common.c:82:15: warning: implicit declaration of function
> ‘json_tokener_parse_ex’ [-Wimplicit-function-declaration]
>    82 |   json_root = json_tokener_parse_ex(
>       |               ^~~~~~~~~~~~~~~~~~~~~
> suricatta/common.c:82:13: warning: assignment to ‘struct json_object *’
> from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
>    82 |   json_root = json_tokener_parse_ex(
>       |             ^
> suricatta/common.c:84:23: warning: implicit declaration of function
> ‘json_tokener_get_error’ [-Wimplicit-function-declaration]
>    84 |  } while ((json_res = json_tokener_get_error(json_tokenizer)) ==
>       |                       ^~~~~~~~~~~~~~~~~~~~~~
> suricatta/common.c:85:4: error: ‘json_tokener_continue’ undeclared (first
> use in this function)
>    85 |    json_tokener_continue);
>       |    ^~~~~~~~~~~~~~~~~~~~~
> suricatta/common.c:85:4: note: each undeclared identifier is reported only
> once for each function it appears in
> suricatta/common.c:86:18: error: ‘json_tokener_success’ undeclared (first
> use in this function); did you mean ‘json_tokener_error’?
>    86 |  if (json_res != json_tokener_success) {
>       |                  ^~~~~~~~~~~~~~~~~~~~
>       |                  json_tokener_error
> suricatta/suricatta.c:17:10: fatal error: json-c/json.h: No such file or
> directory
>    17 | #include <json-c/json.h>
> 
> 
>    - host machine (OS/release) --Linux MINT20
>    - version of Buildroot--2021.11
>    - target for which the build fails--raspberry pi b
>    - package(s) for which the build fails--swupdate
>    - the command that fails and its output--as posted above
>    - any information you think that may be relevant
> 
> 
> Thanks
> Chris

Seems suricatta depens on json-c, simple enable additional

	BR2_PACKAGE_JSON_C=y

in your .config file (or json-c via 'make menuconfig')...

Note: swupdate has already an optional dependency on json-c
(see [1]) but an hard dependency for an changed swupdate
config (via 'make swupdate-menuconfig' is hard to express
in buildroot)...

Regards,
Peter

[1] https://git.buildroot.net/buildroot/tree/package/swupdate/swupdate.mk#n42
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-01-29 19:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  3:59 [Buildroot] swupdate suricatta build error Chris
2022-01-29 19:07 ` Peter Seiderer [this message]

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=20220129200755.17188a26@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@buildroot.org \
    --cc=cheart0@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox