All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libnl: bump to version 3.2.17
Date: Tue, 8 Jan 2013 18:15:48 +0100	[thread overview]
Message-ID: <20130108181548.113e00bb@skate> (raw)
In-Reply-To: <1357332135-3087-1-git-send-email-gustavo@zacarias.com.ar>

Dear Gustavo Zacarias,

On Fri,  4 Jan 2013 17:42:15 -0300, Gustavo Zacarias wrote:
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>  package/libnl/libnl.mk |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

libnl is causing a recurrent build failure:

  CC     netfilter/exp_obj.lo
netfilter/exp_obj.c: In function 'exp_dump_details':
netfilter/exp_obj.c:271:23: error: 'NF_CT_EXPECT_PERMANENT' undeclared (first use in this function)
netfilter/exp_obj.c:271:23: note: each undeclared identifier is reported only once for each function it appears in
netfilter/exp_obj.c:273:23: error: 'NF_CT_EXPECT_INACTIVE' undeclared (first use in this function)
netfilter/exp_obj.c:275:23: error: 'NF_CT_EXPECT_USERSPACE' undeclared (first use in this function)

See:

  http://autobuild.buildroot.org/results/28f23910e2c2090e6f37e8d6a26cdb5adf9615c2/
  http://autobuild.buildroot.org/results/b8d0b9e7d5ea3a8f3c4ba29faeee0434ea5a1111/

Could you have a look?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-01-08 17:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 20:42 [Buildroot] [PATCH] libnl: bump to version 3.2.17 Gustavo Zacarias
2013-01-04 20:46 ` Peter Korsgaard
2013-01-04 20:52   ` Gustavo Zacarias
2013-01-04 21:10     ` Peter Korsgaard
2013-01-08 17:15 ` Thomas Petazzoni [this message]
2013-01-08 17:46   ` Gustavo Zacarias

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=20130108181548.113e00bb@skate \
    --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 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.