All of lore.kernel.org
 help / color / mirror / Atom feed
From: "SŽébastien Cramatte" <scramatte@zensoluciones.com>
To: netfilter@vger.kernel.org
Cc: Jan Engelhardt <jengelh@medozas.de>
Subject: Re: ipp2 won't compile with lastest  iptables from  git
Date: Fri, 04 Jul 2008 21:11:07 +0200	[thread overview]
Message-ID: <486E75CB.7060301@zensoluciones.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0807041846060.31959@fbirervta.pbzchgretzou.qr>

Jan Engelhardt escribió:
> On Friday 2008-07-04 17:33, S?ébastien Cramatte wrote:
>
>   
>> Hi
>>
>> I can't compile ipp2p wit the latest iptables from git !
>>     
>
> The latest ipp2p version is included in Xtables-addons.
>
>   
>> I've applied the ipp2p patch from  patch-o-matic  git  ... When I open
>> libipt_ipp2.c it seems that the source already has the required change for
>> iptables 1.4.x ... biut unfortuanteley doesn't works for me !
>>     
>
> Because pom-ng is old and not updated.
>   
Yes ! But my problem is that I must package a kernel that use initramfs  
with all included modules.
As pom-ng patch the kernel source  was nice for me ...

Moreover I can't use Xtables-addons directly because I compile on  
dedicaded box that use another kernel than the target !
My target box boot from Compact Flash to memory and doesn't have  
development tools installed !

Any solutions ?


  reply	other threads:[~2008-07-04 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04 15:33 ipp2 won't compile with lastest iptables from git SŽébastien Cramatte
2008-07-04 16:46 ` Jan Engelhardt
2008-07-04 19:11   ` SŽébastien Cramatte [this message]
2008-07-04 19:25     ` Jan Engelhardt
2008-07-04 19:29       ` SŽébastien Cramatte
2008-07-04 20:17         ` Jan Engelhardt
2008-07-04 20:26           ` SŽébastien Cramatte

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=486E75CB.7060301@zensoluciones.com \
    --to=scramatte@zensoluciones.com \
    --cc=jengelh@medozas.de \
    --cc=netfilter@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 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.