All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amin Azez <azez@ufomechanic.net>
To: Amin Azez <azez@ufomechanic.net>
Cc: netfilter-devel@lists.netfilter.org, Patrick McHardy <kaber@trash.net>
Subject: quick fix Re: Fix --with-kernel for libnfnetlink
Date: Wed, 26 Jul 2006 15:11:25 +0100	[thread overview]
Message-ID: <44C7780D.6000109@ufomechanic.net> (raw)
In-Reply-To: <44C776F8.10904@ufomechanic.net>

I'm an idiot.
Sorry.

(Takes hammer for quick fix. Ouch. Fix complete).

Sam


* Amin Azez wrote, On 26/07/06 15:06:
> Sorry to bring this up again...
> 
> * Pablo Neira Ayuso wrote, On 21/04/06 12:09:
>> Why do you need this parameter? the netfilter libraries don't require
>> kernel headers anymore since they are already bundled in the package
>> provided. For example, see include/libnfnetlink/linux_nfnetlink.h. We
>> have had several problems with iptables and the kernel headers in the
>> past: compilation warnings, breakages... That is the reason why we
>> decided to do so.
>>
>> On the other hand, autogen.sh automates the copy of these headers,
>> so you could choose them via KERNEL_DIR but you need some important
>> reason to do that.
> 
> 
> Current (svn) autogen.sh is hard wired to use the currently booted kernel.
> 
> I'm all for not keeping a copy in the SVN tree, but why presume that the
> one in the booted kernel is the one we want? Isn't this just another
> reason to have --with-kernel back; as we are not copying old userland
> so-called kernel header files?
> 
> Since my 2.6.11 work (which is booted) I'm now working towards 2.6.17,
> and the differences are:
> 
> -#define NFNL_SUBSYS_CTHELPER           5
> -#define NFNL_SUBSYS_COUNT              6
> +#define NFNL_SUBSYS_COUNT              5
> 
>  #ifdef __KERNEL__
> 
> @@ -165,6 +164,7 @@
>         __res;                                                          \
>  })
> 
> +extern int nfnetlink_has_listeners(unsigned int group);
> 
> 
> Which seem important; it is a mistake for autogen.sh to have copied the
> file for the booted kernel.
> 
> I did wonder if libnfnetlink should use text labels instead of symbols,
> and have the dynamic (or at least unpredicatbale) values fetched from
> the kernel and stored as int's instead of constants in libnfnetlink
> 
> It would solve this problem.
> 
> Sam
> 
> 

      reply	other threads:[~2006-07-26 14:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 15:25 Fix --with-kernel for libnfnetlink David Vogt
2006-04-20 16:33 ` Amin Azez
2006-04-20 16:50 ` Sven-Haegar Koch
2006-04-20 18:51   ` Patrick McHardy
2006-04-20 18:53     ` Patrick McHardy
2006-04-20 19:38     ` KOVACS Krisztian
2006-04-20 22:52       ` Patrick McHardy
2006-04-21 15:25         ` Pablo Neira Ayuso
2006-04-21 20:02           ` Harald Welte
2006-04-20 19:34 ` Patrick McHardy
2006-04-21  7:21   ` David Vogt
2006-04-21 11:09     ` Pablo Neira Ayuso
2006-04-21 12:48       ` Amin Azez
2006-04-21 13:12         ` Pablo Neira Ayuso
2006-04-21 13:56           ` Amin Azez
2006-07-26 14:06       ` Amin Azez
2006-07-26 14:11         ` Amin Azez [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=44C7780D.6000109@ufomechanic.net \
    --to=azez@ufomechanic.net \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.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 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.