All of lore.kernel.org
 help / color / mirror / Atom feed
From: Friedrich Lobenstock <fl@fl.priv.at>
To: johnpol@2ka.mipt.ru
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: pom-20040409: patches that break iptables-1.2.9-20040409, kernel 2.4.25 or pom's runme
Date: Sun, 11 Apr 2004 13:54:41 +0200	[thread overview]
Message-ID: <40793201.4070906@fl.priv.at> (raw)
In-Reply-To: <20040411155523.1fd06a78.johnpol@2ka.mipt.ru>

Evgeniy Polyakov wrote on 11.04.2004 13:55 MET:
> On Sun, 11 Apr 2004 13:15:03 +0200 Friedrich Lobenstock <fl@fl.priv.at> wrote:
> 
>>I want to inform you that the following patches in pom-20040409,
>>which btw apply cleanly to the kernel 2.4.25, do break the
>>compilation of iptables-1.2.9-20040409:
> 
> 
>>   3) base/osf
>>        breaks the extension in iptables - see log below
> 
> 
>>Extensions found: IPv4:IPV4OPTSSTRIP IPv4:NETLINK IPv4:addrtype 
>>IPv4:condition IPv4:fuzzy IPv4:ipv4options IPv4:mport
>>  IPv4:nth IPv4:osf IPv4:pool IPv4:POOL IPv4:psd IPv4:quota
>>  IPv4:random 
>>IPv4:recent IPv4:time IPv4:u32 IPv6:REJECT IPv
>>6:ah IPv6:esp IPv6:frag IPv6:fuzzy IPv6:ipv6header IPv6:nth IPv6:hbh 
>>IPv6:dst IPv6:random IPv6:rt
>>[...]
>>cc -O2 -Wall -Wunused -I/usr/src/linux/include -Iinclude/ 
>>-DIPTABLES_VERSION=\"1.2.9-20040409\"  -fPIC -o extensions/
>>libipt_osf_sh.o -c extensions/libipt_osf.c
>>extensions/libipt_osf.c: In function `parse':
>>extensions/libipt_osf.c:106: error: `IPT_OSF_NETLINK' undeclared
>>(first use in this function)
>>extensions/libipt_osf.c:106: error: (Each undeclared identifier is
>>reported only once
>>extensions/libipt_osf.c:106: error: for each function it appears in.)
>>make: *** [extensions/libipt_osf_sh.o] Error 1
> 
> 
> What sources do you use?
> You need CVS pom-ng + CVS iptables/extensions/libipt_osf.c for
> successfull compilation.
> 
> IPT_OSF_NETLINK is defined in
> patch-o-matic-ng/osf/linux/include/linux/netfilter_ipv4/ipt_osf.h:
> 
> #define IPT_OSF_NETLINK		8
> 
> 
> With CVS pom-ng and CVS iptables/extensions/libipt_osf.c I can compile
> both libipt_osf.so and ipt_osf.o ( using my own scripts, but it doesn't
> matter).

I use plain pom, not pom-ng! Otherwise I would have written pom-ng in the 
subject.


> Thank you for review.

You're welcome.

-- 
MfG / Regards
Friedrich Lobenstock

  reply	other threads:[~2004-04-11 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-11 11:15 pom-20040409: patches that break iptables-1.2.9-20040409, kernel 2.4.25 or pom's runme Friedrich Lobenstock
2004-04-11 11:55 ` Evgeniy Polyakov
2004-04-11 11:54   ` Friedrich Lobenstock [this message]
2004-04-11 12:16     ` Evgeniy Polyakov
2004-04-11 20:44 ` Henrik Nordstrom
2004-04-11 20:53   ` Friedrich Lobenstock

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=40793201.4070906@fl.priv.at \
    --to=fl@fl.priv.at \
    --cc=johnpol@2ka.mipt.ru \
    --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.