Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "T. Horsnell (tsh)" <tsh@mrc-lmb.cam.ac.uk>
To: netfilter@lists.netfilter.org
Subject: p.o.m-ng+linux-2.6.2+ctnetlink
Date: Thu, 19 Feb 2004 15:41:14 +0000 (GMT)	[thread overview]
Message-ID: <E1AtqId-000LDX-0I@alf1.lmb.internal> (raw)

Problem using patch-o-matic-ng-20040217 to patch kernel 2.6.2 
and iptables-1.2.9, to include the nfnetlink-ctnetlink-0.13 patch.

When I use .runme to test this patch, it reports:
'Patch nfnetlink-ctnetlink-0.13 applies cleanly'
When I actually install the patch, it reports errors,
but installs it anyway.

Re-make of the kernel then fails:

[root@dev1 linux-2.6.2]# make bzImage
  HOSTCC  scripts/modpost.o
  HOSTLD  scripts/modpost
make[2]: `scripts/fixdep' is up to date.
scripts/kconfig/conf -s arch/i386/Kconfig
net/ipv4/netfilter/Kconfig:593: syntax error, unexpected T_WORD
net/ipv4/netfilter/Kconfig:595: invalid menu option
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** [include/linux/autoconf.h] Error 2

Any advice?

Cheers,
Terry.





=========================================================================
Welcome to Patch-o-matic (1.11)!

Kernel:         /usr/src/linux-2.6.2
Iptables:       /usr/src/iptables

Each patch is a new feature: many have minimal impact, some do not.
Almost every one has bugs, so don't apply what you don't need!
-------------------------------------------------------
Already applied: 

Testing nfnetlink-ctnetlink-0.13... not applied
The nfnetlink-ctnetlink-0.13 patch:
   Author: Harald Welte <laforge@gnumonks.org>, Jay Schulist <jschlst@samba.org>,
   Status: Under development, but stabilizing now.

        Patrick McHardy <kaber@trash.net>
   
   Add recent work by patrick (notifiers, event messages to userspace.
   
-----------------------------------------------------------------
Do you want to apply this patch [N/y/t/f/a/r/b/w/q/?] t
Patch nfnetlink-ctnetlink-0.13 applies cleanly
-----------------------------------------------------------------
Do you want to apply this patch [N/y/t/f/a/r/b/w/q/?] y
ERROR (7 rejects out of 52 hunks)

Excellent! Source trees are ready for compilation.
=========================================================================

Checking whether the patch was actually installed:


=========================================================================
Welcome to Patch-o-matic (1.11)!

Kernel:         /usr/src/linux-2.6.2
Iptables:       /usr/src/iptables

Each patch is a new feature: many have minimal impact, some do not.
Almost every one has bugs, so don't apply what you don't need!
-------------------------------------------------------
Already applied: 

Testing nfnetlink-ctnetlink-0.13... applied

Excellent! Source trees are ready for compilation.
=========================================================================



             reply	other threads:[~2004-02-19 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 15:41 T. Horsnell (tsh) [this message]
2004-02-20  8:54 ` p.o.m-ng+linux-2.6.2+ctnetlink Jozsef Kadlecsik
2004-02-20 17:10   ` p.o.m-ng+linux-2.6.2 pptp rruegner
  -- strict thread matches above, loose matches on Subject: below --
2004-02-19 17:01 p.o.m-ng+linux-2.6.2+ctnetlink Carl Farrington
2004-02-19 19:11 ` p.o.m-ng+linux-2.6.2+ctnetlink T. Horsnell (tsh)

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=E1AtqId-000LDX-0I@alf1.lmb.internal \
    --to=tsh@mrc-lmb.cam.ac.uk \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox