From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/ipset: Fix compile error
Date: Sun, 19 Oct 2014 22:16:57 +0300 [thread overview]
Message-ID: <20141019191657.GB2220@tarshish> (raw)
In-Reply-To: <1413745147-12299-1-git-send-email-bernd.kuhls@t-online.de>
Hi Bernd,
On Sun, Oct 19, 2014 at 08:59:07PM +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(+)
>
> diff --git a/package/ipset/ipset.mk b/package/ipset/ipset.mk
> index d3dbc67..b1518f4 100644
> --- a/package/ipset/ipset.mk
> +++ b/package/ipset/ipset.mk
> @@ -13,4 +13,6 @@ IPSET_AUTORECONF = YES
> IPSET_LICENSE = GPLv2
> IPSET_LICENSE_FILES = COPYING
>
> +IPSET_CONF_ENV = ax_cv_cflags_gcc_option__Winline=""
> +
> $(eval $(autotools-package))
Instead of squashing each type of compiler warning, why not remove -Werror
entirely? It's not that useful when you only want to build the package.
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 -
next prev parent reply other threads:[~2014-10-19 19:16 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 [this message]
2014-10-26 15:42 ` Thomas Petazzoni
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=20141019191657.GB2220@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.