Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] xtables-addons does not build for arm kernel 4.1.4
Date: Mon, 17 Aug 2015 23:52:18 +0200	[thread overview]
Message-ID: <87lhd98twt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20150817185012.2051aa10@pcviktorin.fit.vutbr.cz> (Jan Viktorin's message of "Mon, 17 Aug 2015 18:50:12 +0200")

>>>>> "Jan" == Jan Viktorin <viktorin@rehivetech.com> writes:

 > Hello Gustavo,
 > I am trying to compile xtables-addons by Buildroot, however, I get a lot
 > of "undefined!" warnings and some errors.

 > I build with:
 > - Buildroot (master: 15a53b93a034af78)
 > - internal toolchain
 > - Linux 4.1.4.

 > The Buildroot is patched by http://lists.busybox.net/pipermail/buildroot/2015-August/137485.html
 > for the olinuxino lime2 support. However, the same issues come with olimex_a20_olinuxino_lime_defconfig.

 > My setup is:

 > $ make olimex_a20_olinuxino_lime2_defconfig
 > $ make menuconfig
 >   enable Target packages/Network Applications/xtables-addons
 > $ make

 > And I end up with:

> buildroot-a20/output/build/xtables-addons-2.7/extensions/compat_xtables.mod.c:9:2: error: unknown field ?name? specified in initializer
 >   .name = KBUILD_MODNAME,

The problem is that you don't have modules (CONFIG_MODULES=y) support
enabled in your kernel, as the sunxi_defconfig in the kernel until very
recently didn't enable that - But it is naturally needed to build the
xtables-addons modules.

Arguably Buildroot should automatically enable this for you when
enabling the xtables-addons package, similar to how it is done for the
netfilter options even though it is quite a "big" option to enable
behind your back. Alternatively we could simply error out with a
sensible message like it was recently done for the pkg-kernel-module
infrastructure.


 > I can build xtables-addons from git (tag 2.7, e277360) for both Linux 4.1.4 and 4.1.5 on
 > x86_64 by the standard xtables-addons build-system (without Buildroot).

You most likely have modules support in your x86-64 kernel.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2015-08-17 21:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 16:50 [Buildroot] xtables-addons does not build for arm kernel 4.1.4 Jan Viktorin
2015-08-17 21:52 ` Peter Korsgaard [this message]
2015-08-17 22:35   ` Jan Viktorin
2015-08-19 13:14   ` [Buildroot] [PATCH v1 0/2] Checking whether a certain CONFIG_* is set Jan Viktorin
2015-08-19 13:14     ` [Buildroot] [PATCH v1 1/2] pkg-utils: Define KCONFIG_ASSERT_OPT macro Jan Viktorin
2015-08-19 19:16       ` Yann E. MORIN
2015-08-19 13:14     ` [Buildroot] [PATCH v1 2/2] xtables-addons: test CONFIG_MODULES=y in the kernel Jan Viktorin
2015-08-19 17:46     ` [Buildroot] [PATCH v1 0/2] Checking whether a certain CONFIG_* is set Thomas Petazzoni
2015-08-19 19:05       ` Yann E. MORIN
2015-08-19 19:08         ` Thomas Petazzoni
2015-08-19 19:21           ` Yann E. MORIN
2015-08-19 20:23             ` Thomas Petazzoni
2015-08-19 21:05         ` Peter Korsgaard
2015-08-21 13:22           ` Yann E. MORIN
2015-08-21 13:41             ` Jeremy Rosen
2015-08-21 20:28             ` Peter Korsgaard
2015-08-21 21:05               ` Yann E. MORIN
2015-08-21 22:17                 ` Peter Korsgaard

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=87lhd98twt.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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