Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/ipset: Fix compile error
Date: Sun, 26 Oct 2014 16:42:54 +0100	[thread overview]
Message-ID: <20141026164254.2f4f8591@free-electrons.com> (raw)
In-Reply-To: <1413745147-12299-1-git-send-email-bernd.kuhls@t-online.de>

Dear Bernd Kuhls,

On Sun, 19 Oct 2014 20:59:07 +0200, Bernd Kuhls wrote:
> Error occured with an allyespackageconfig setup:
> 
> In file included from print.c:19:0:
> print.c: In function 'ipset_print_ip':
> ../include/libipset/data.h:150:1: error: inlining failed in call to 'ipset_data_test': call is unlikely and code size would grow [-Werror=inline]
>  ipset_data_test(const struct ipset_data *data, enum ipset_opt opt)
>  ^
> print.c:273:21: error: called from here [-Werror=inline]
>   if (ipset_data_test(data, cidropt)) {
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
>  package/ipset/ipset.mk |    2 ++
>  1 file changed, 2 insertions(+)

To fix the same problem, I've applied a slightly different fix, that
simply removes -Werror altogether.

See
http://git.buildroot.net/buildroot/commit/?id=a923b44112aa3bfdb42b12cc1bd2712a263c1a0c.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-10-26 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-19 18:59 [Buildroot] [PATCH 1/1] package/ipset: Fix compile error Bernd Kuhls
2014-10-19 19:16 ` Baruch Siach
2014-10-26 15:42 ` Thomas Petazzoni [this message]
2014-10-26 16:00   ` Baruch Siach
2014-10-26 16:52     ` Thomas Petazzoni
2014-10-26 19:17       ` Baruch Siach

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=20141026164254.2f4f8591@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox