From: mortar <slacklist@op.pl>
To: netfilter@lists.netfilter.org
Subject: Re[2]: make error with iptables 1.2.11
Date: Wed, 30 Jun 2004 03:08:26 +0200 [thread overview]
Message-ID: <145030924.20040630030826@op.pl> (raw)
In-Reply-To: <200406292309.38461.Antony@Soft-Solutions.co.uk>
Witam
Wednesday, June 30, 2004, 12:09:38 AM, you wrote:
AS> Okay - that narrows it down. Anyone else here have experience with kernel
AS> 2.4.26 and iptables 1.2.11? I can't offer any advice on this one...
I have 2.4.26 and iptables 1.2.11. I patched kernel and iptables
sources with latest pom-ng and then succesfully builded both. I'm using
Slackware Linux with gcc 3.3.4. Here is step by step how I make this
things works ;)
1. Get kernel 2.4.26 sources, and decompress it to
/usr/src/linux-2.4.26
2. Make a symbolic link
#ln -s /usr/src/linux-2.4.26 linux
3. Get iptables sources
#wget http://www.iptables.org/files/iptables-1.2.11.tar.bz2
and decompress it to /usr/src/iptables-1.2.11
4. Make a symbolic link
#ln -s /usr/src/iptables-1.2.11 iptables
5. Get lates p-o-m-ng
#wget http://www.netfilter.org/files/patch-o-matic-ng-20040621.tar.bz2
and decompress it to /usr/src/patch-o-matic-ng-20040621
6. cd /usr/src/patch-o-matic-ng-20040621
7. Now patch your sources with any extensions you want (i suggest you
to choose only what your realy need). For example:
#KERNEL_DIR=/usr/src/linux ./runme string
#KERNEL_DIR=/usr/src/linux ./runme CONNMARK
...
8. And now the most important step ;)
#cd /usr/src/iptables
#make BINDIR=/sbin LIBDIR=/usr/lib
#make BINDIR=/sbin LIBDIR=/usr/lib install
9. If everything is fine, you can build your kernel.
10. If not ... maybe try older (or newer) version of gcc.
I hope this will help you.
(Sorry for my poooooore english :)
--
Pozdrawiam
Marcin mailto:slacklist@op.pl
next prev parent reply other threads:[~2004-06-30 1:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 20:45 make error with iptables 1.2.11 Chamara Gunaratne
2004-06-29 21:00 ` Antony Stone
2004-06-29 21:31 ` Chamara Gunaratne
2004-06-29 22:09 ` Antony Stone
2004-06-29 23:42 ` Chamara Gunaratne
2004-06-30 1:08 ` mortar [this message]
2004-06-30 17:05 ` Chamara Gunaratne
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=145030924.20040630030826@op.pl \
--to=slacklist@op.pl \
--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 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.