netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wiktor Kolodziej <wiktor@zhr.pl>
To: netfilter-devel@vger.kernel.org
Subject: Re: [xtables-addons] extensions in a non-modular kernel
Date: Sat, 19 Dec 2009 21:45:08 +0100	[thread overview]
Message-ID: <6fbd78aa0912191245ja7a06c8wb07c2910ca9245ad@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.01.0912081057250.15262@obet.zrqbmnf.qr>

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

2009/12/8 Jan Engelhardt <jengelh@medozas.de>:
> On Thursday 2009-12-03 11:54, Wiktor Kolodziej wrote:
>
>>Is there any easy way to compile extensions into a non-modular kernel?
>
> Depends on the definition of easy.
>
>>I've found in Jan's "An Introduction to Xtables-addons" that this is
>>possible, but can you please give me some more info how to do it?
>>What do you mean by "editing some kernel Makefile to descend into
>>xtables-addons/extensions" ?
>
> ln -s ~/xtables-addons ~/linux/net/netfilter/
> echo "obj-y += xtables-addons/extensions/"
>        >>~/linux/net/netfilter/Makefile
>
> Granted it does not stop there, one needs to modify extensions/Kbuild
> because it depends on symbols from mconfig (oh my) which would need to
> be exchanged to obj-y or something.

Thanks for helping with that.
I've created a script that does it automatically.
I'm attaching it if somebody needs to quickly build a non-modular
kernel with xtables-addons.

Wiktor.

[-- Attachment #2: xtables.sh --]
[-- Type: application/x-sh, Size: 2745 bytes --]

      reply	other threads:[~2009-12-19 20:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 10:54 [xtables-addons] extensions in a non-modular kernel Wiktor Kolodziej
2009-12-08  9:59 ` Jan Engelhardt
2009-12-19 20:45   ` Wiktor Kolodziej [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=6fbd78aa0912191245ja7a06c8wb07c2910ca9245ad@mail.gmail.com \
    --to=wiktor@zhr.pl \
    --cc=netfilter-devel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).