From: "Takuya Satoh" <taka0038@yahoo.com>
To: netfilter@lists.samba.org
Subject: Current CVS version doesn't compile
Date: Fri, 24 May 2002 11:39:15 +0900 [thread overview]
Message-ID: <002201c202cc$32e7ef40$f3c4b5cb@k768> (raw)
iptables-1.2.6a-cvs020520:
cc -O2 -Wall -Wunused -I/usr/src/linux/include -Iinclude/ -DNETFILTER_VERSIO
N=\"1.2.7\" -fPIC -o extensions/libipt_REJECT_sh.o -c
extensions/libipt_REJECT.c
extensions/libipt_REJECT.c: In function `init':
extensions/libipt_REJECT.c:92: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c: In function `parse':
extensions/libipt_REJECT.c:128: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c:143: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c: In function `print':
extensions/libipt_REJECT.c:173: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c:174: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c:174: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c:174: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c:174: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c: In function `save':
extensions/libipt_REJECT.c:189: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c:190: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c:190: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c:190: structure has no member named
`fake_source_address'
extensions/libipt_REJECT.c:190: structure has no member named
`fake_source_address'
make: *** [extensions/libipt_REJECT_sh.o] Error 1
Taka
next reply other threads:[~2002-05-24 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 2:39 Takuya Satoh [this message]
2002-06-14 4:12 ` Current CVS version doesn't compile Fabrice MARIE
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='002201c202cc$32e7ef40$f3c4b5cb@k768' \
--to=taka0038@yahoo.com \
--cc=netfilter@lists.samba.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