All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Cc: jengelh@computergmbh.de, netfilter-devel@vger.kernel.org
Subject: Re: kernel-source required?
Date: Thu, 10 Jan 2008 16:50:46 +0100	[thread overview]
Message-ID: <47863ED6.2000206@trash.net> (raw)
In-Reply-To: <200801100922.m0A9MW2Z011677@toshiba.co.jp>

Yasuyuki KOZAKAI wrote:
> From: Jan Engelhardt <jengelh@computergmbh.de>
> Date: Wed, 9 Jan 2008 18:30:36 +0100 (CET)
> 
>> just now as an IRC user posted about a compilation error, the only 
>> situation that I could think of to load to this error was a missing 
>> kernel source tree.
>> Since many Xtables header files are copied to the iptables source tree, 
>> yet `make KERNEL_DIR=somethinginvalid` gives a compiler error because it 
>> cannot find <linux/compiler.h> (required by ip_tables.h).
> 
> I wonder why recent (at least, Fedora Core 7) distributed kernel header
> package for user programs does not include /usr/include/linux/compiler.h .

Debian doesn't have it either.

>> So I wonder, do we actually support building iptables without a 
>> kernel source tree?
> 
> I prefer to keep people easy to try newer iptables as possible.
> We can add include/linux/compiler.h to iptables or remove __user, etc. from
> headers of iptables.

Or simply define the missing annotations in xtables.h.


      parent reply	other threads:[~2008-01-10 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 17:30 kernel-source required? Jan Engelhardt
2008-01-10  9:22 ` Yasuyuki KOZAKAI
     [not found] ` <200801100922.m0A9MW2Z011677@toshiba.co.jp>
2008-01-10 15:50   ` Patrick McHardy [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=47863ED6.2000206@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@computergmbh.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=yasuyuki.kozakai@toshiba.co.jp \
    /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.