From: "David Busby" <busby@pnts.com>
To: techlists@alberni.net,
Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: Iptables 1.2.8 Compile Errors
Date: Wed, 2 Jul 2003 12:27:37 -0700 [thread overview]
Message-ID: <07ac01c340d0$06a7a090$1100000a@busbydev> (raw)
In-Reply-To: 200307021153.AA850591966@mail.alberni.net
Show us the errors?
----- Original Message -----
From: "Aaron Clausen" <techlists@alberni.net>
To: "Netfilter Mailing List" <netfilter@lists.netfilter.org>
Sent: Wednesday, July 02, 2003 11:53
Subject: Iptables 1.2.8 Compile Errors
> I'm trying to compile Iptables 1.2.8 for a 2.4.21 kernel that has had
patch-o-matic-20030107 applied to it. The kernel compiles fine, but I'm
continually getting errors compiling libipt_ROUTE.c. I realize that the
easiest thing to do is to simply not enable this extension in the kernel,
and yet turning it off in the config doesn't do anything. Does anybody have
a solution?
>
> --
> Aaron Clausen
next prev parent reply other threads:[~2003-07-02 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 18:53 Iptables 1.2.8 Compile Errors Aaron Clausen
2003-07-02 19:27 ` David Busby [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-02 22:26 Aaron Clausen
2003-07-02 22:54 ` Sebastian
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='07ac01c340d0$06a7a090$1100000a@busbydev' \
--to=busby@pnts.com \
--cc=netfilter@lists.netfilter.org \
--cc=techlists@alberni.net \
/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