From: "Sebastian" <netfilter@basti79.de>
To: Netfilter Mailinglist <netfilter@lists.netfilter.org>
Subject: RE: Iptables 1.2.8 Compile Errors
Date: Thu, 3 Jul 2003 00:54:08 +0200 [thread overview]
Message-ID: <000001c340ec$d9d377c0$0200a8c0@basti79> (raw)
In-Reply-To: <200307021526.AA497484112@mail.alberni.net>
Hello...
I'm not so familiar with the sources, but I think the problem is the
different definition of the struct ipt_route_target_info (in
include/linux/netfilter_ipv4/ipt_ROUTE.h) between POM you use and the
laterst CVS. The patch-o-matic 20030107 was release long befor
iptables-1.2.8, you should probably try a CVS version of patch-o-matic.
Greets
Sebastian.
> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org] On Behalf Of
> Aaron Clausen
> Sent: Thursday, July 03, 2003 12:26 AM
> To: Netfilter Mailing List; David Busby
> Subject: Re: Iptables 1.2.8 Compile Errors
>
>
> ---------- Original Message ----------------------------------
> From: "David Busby" <busby@pnts.com>
> Reply-To: "David Busby" <busby@pnts.com>
> Date: Wed, 2 Jul 2003 12:27:37 -0700
>
> >Show us the errors?
>
> Sorry, here's the whole error:
>
> ld -shared -o extensions/libipt_NETMAP.so
> extensions/libipt_NETMAP_sh.o cc -O2 -Wall -Wunused
> -I/usr/src/linux/include -Iinclude/
> -DIPTABLES_VERSION=\"1.2.8\" -fPIC -o
> extensions/libipt_ROUTE_sh.o -c extensions/libipt_ROUTE.c
> extensions/libipt_ROUTE.c: In function `init':
> extensions/libipt_ROUTE.c:44: structure has no member named `oif'
> extensions/libipt_ROUTE.c:45: structure has no member named `iif'
> extensions/libipt_ROUTE.c:46: structure has no member named `gw'
> extensions/libipt_ROUTE.c: In function `parse':
> extensions/libipt_ROUTE.c:73: structure has no member named `oif'
> extensions/libipt_ROUTE.c:76: structure has no member named `oif'
> extensions/libipt_ROUTE.c:78: structure has no member named `oif'
> extensions/libipt_ROUTE.c:78: structure has no member named `oif'
> extensions/libipt_ROUTE.c:78: structure has no member named `oif'
> extensions/libipt_ROUTE.c:91: structure has no member named `iif'
> extensions/libipt_ROUTE.c:94: structure has no member named `iif'
> extensions/libipt_ROUTE.c:96: structure has no member named `iif'
> extensions/libipt_ROUTE.c:96: structure has no member named `iif'
> extensions/libipt_ROUTE.c:96: structure has no member named `iif'
> extensions/libipt_ROUTE.c:105: structure has no member named `gw'
> extensions/libipt_ROUTE.c: In function `print':
> extensions/libipt_ROUTE.c:142: structure has no member named `oif'
> extensions/libipt_ROUTE.c:143: structure has no member named `oif'
> extensions/libipt_ROUTE.c:145: structure has no member named `iif'
> extensions/libipt_ROUTE.c:146: structure has no member named `iif'
> extensions/libipt_ROUTE.c:148: structure has no member named `gw'
> extensions/libipt_ROUTE.c:149: structure has no member named `gw'
> extensions/libipt_ROUTE.c: In function `save':
> extensions/libipt_ROUTE.c:161: structure has no member named `oif'
> extensions/libipt_ROUTE.c:162: structure has no member named `oif'
> extensions/libipt_ROUTE.c:164: structure has no member named `iif'
> extensions/libipt_ROUTE.c:165: structure has no member named `iif'
> extensions/libipt_ROUTE.c:167: structure has no member named `gw'
> extensions/libipt_ROUTE.c:168: structure has no member named `gw'
> make: *** [extensions/libipt_ROUTE_sh.o] Error 1
>
> --
> Aaron Clausen
>
>
next prev parent reply other threads:[~2003-07-02 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 22:26 Iptables 1.2.8 Compile Errors Aaron Clausen
2003-07-02 22:54 ` Sebastian [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-02 18:53 Aaron Clausen
2003-07-02 19:27 ` David Busby
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='000001c340ec$d9d377c0$0200a8c0@basti79' \
--to=netfilter@basti79.de \
--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.