From: "R. Sterenborg" <rsterenborg@xs4all.nl>
To: netfilter@lists.netfilter.org
Subject: RE: ftp server issue, trying to DL 1.2.7a
Date: Fri, 6 Sep 2002 08:05:29 +0200 [thread overview]
Message-ID: <000801c2556b$671f2070$0401000a@win2k> (raw)
In-Reply-To: <NEENJAPFEAIEMGMNIGFLAELBCCAA.rwideman@austin.rr.com>
> GREAT, Thanks
You're welcome :o)
> new problem...i compiled the kernel and i get these errors:
<snip>
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall
> -Wstrict-prototypes -Wno-tri
> graphs -O2 -fno-strict-aliasing -fno-common
> -fomit-frame-pointer -pipe -mpre
> ferred-stack-boundary=2 -march=i586 -nostdinc -I
> /usr/lib/gcc-lib/i386-redhat-linux/2.96/include
> -DKBUILD_BASENAME=ipt_helper
> -c -o ipt_helper.o ipt_helper.c
> ipt_helper.c: In function `match':
> ipt_helper.c:46: wrong type argument to unary exclamation mark
> ipt_helper.c:51: incompatible types in assignment
> ipt_helper.c:67: structure has no member named `name'
> ipt_helper.c:68: structure has no member named `name'
> make[3]: *** [ipt_helper.o] Error 1
> make[3]: Leaving directory `/usr/src/linux/net/ipv4/netfilter'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux/net/ipv4/netfilter'
> make[1]: *** [_subdir_ipv4/netfilter] Error 2
> make[1]: Leaving directory `/usr/src/linux/net'
> make: *** [_dir_net] Error 2
>
Uh.. Dunno. I'm still no guru :o) I guess there's some patch missing ?
I started patching with ./runme submitted, and I didn't have the
problem that you have (but I did when I didn't start with
submitted...).
I read somewhere about a week ago that patching should start with
submitted, but if you go further down the line (pending, base, extra)
it looks like it checks if the kernel is patched with options of the
previous stage, only it continues where the previous one stopped.
If that is really so, then I don't understand why patching should
start at submitted instead of, let's say extra.
Can someone please explain how this actually works : if I want patches
from extra, should I really start with submitted ?
Rob
next prev parent reply other threads:[~2002-09-06 6:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002901c2551c$f5dd4700$3200a8c0@fcol.com>
2002-09-05 21:34 ` ftp server issue, trying to DL 1.2.7a Rob
2002-09-05 22:37 ` R. Sterenborg
2002-09-06 3:49 ` Rob
2002-09-06 6:05 ` R. Sterenborg [this message]
2002-09-10 3:51 Rob
-- strict thread matches above, loose matches on Subject: below --
2002-09-05 17:29 Rob
2002-09-05 18:30 ` Rob
2002-09-06 1:50 ` Fabrice MARIE
2002-09-05 18:32 ` Antony Stone
2002-09-05 22:00 ` wickedsun
2002-09-05 18:33 ` Ramin Alidousti
2002-09-05 19:57 ` Alistair Tonner
2002-09-06 9:39 ` Anders Fugmann
2002-09-07 12:38 ` wickedsun
2002-09-07 13:18 ` Anders Fugmann
2002-09-07 15:33 ` wickedsun
2002-09-07 15:40 ` Alistair Tonner
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='000801c2556b$671f2070$0401000a@win2k' \
--to=rsterenborg@xs4all.nl \
--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