All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] json-c: bump version to json-c-0.12-20140410
Date: Wed, 15 Apr 2015 06:13:48 +0300	[thread overview]
Message-ID: <20150415031347.GA30380@tarshish> (raw)
In-Reply-To: <552DA110.5050001@proximus.be>

Hi Sagaert Johan,

On Wed, Apr 15, 2015 at 01:21:52AM +0200, Johan Sagaert wrote:
> Baruch Siach schreef op 14/04/2015 om 11:15:
> >It seems this packages builds with -Werror, hence the need for this patch 
> >to avoid build breakage. A better solution, in my opinion, is to remove 
> >-Werror.
> 
> i tried
> diff --git a/Makefile.am.inc b/Makefile.am.inc
> index fec591b..61db1d2 100644
> --- a/Makefile.am.inc
> +++ b/Makefile.am.inc
> @@ -1,2 +1,2 @@
> -AM_CFLAGS = -Wall -Werror -Wno-error=deprecated-declarations -Wextra
> -Wwrite-strings -Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE -D_REENTRANT
> +AM_CFLAGS = -Wall -Wno-error=deprecated-declarations -Wextra
> -Wwrite-strings -Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE -D_REENTRANT
> 
> but this seems to yield this unexpected error.
> 
> >>> json-c json-c-0.12-20140410 Building
> PATH="/home/buildroot12git/output/host/bin:/home/buildroot12git/output/host/sbin:/home/buildroot12git/output/host/usr/bin:/home/buildroot12git/output/host/usr/sbin:/root/google-cloud-sdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/buildroot12git/output/build/host-cmake-3.0.2/bin"
> /usr/bin/make -j1  -C
> /home/buildroot12git/output/build/json-c-json-c-0.12-20140410/
> make[1]: Entering directory
> `/home/buildroot12git/output/build/json-c-json-c-0.12-20140410'
>  cd . && /bin/sh
> /home/buildroot12git/output/build/json-c-json-c-0.12-20140410/missing
> automake-1.14 --gnu Makefile
> /home/buildroot12git/output/build/json-c-json-c-0.12-20140410/missing: line
> 81: automake-1.14: command not found
> WARNING: 'automake-1.14' is missing on your system.
>          You should only need it if you modified 'Makefile.am' or
>          'configure.ac' or m4 files included by 'configure.ac'.
>          The 'automake' program is part of the GNU Automake package:
>          <http://www.gnu.org/software/automake>
>          It also requires GNU Autoconf, GNU m4 and Perl in order to run:
>          <http://www.gnu.org/software/autoconf>
>          <http://www.gnu.org/software/m4/>
>          <http://www.perl.org/>
> make[1]: *** [Makefile.in] Error 127
> make[1]: Leaving directory
> `/home/buildroot12git/output/build/json-c-json-c-0.12-20140410'
> make: ***
> [/home/buildroot12git/output/build/json-c-json-c-0.12-20140410/.stamp_built]
> Error 2
> return of make was 2
> 
> I don't see why.

Please try adding

	JSON_C_AUTORECONF = YES

to your .mk file.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      reply	other threads:[~2015-04-15  3:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14  9:10 [Buildroot] [PATCH 1/1] json-c: bump version to json-c-0.12-20140410 Sagaert Johan
2015-04-14  9:15 ` Baruch Siach
2015-04-14 23:21   ` Johan Sagaert
2015-04-15  3:13     ` Baruch Siach [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=20150415031347.GA30380@tarshish \
    --to=baruch@tkos.co.il \
    --cc=buildroot@busybox.net \
    /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.