From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: iptables warnings on 64 bit
Date: Mon, 14 Apr 2008 08:54:47 +0200 [thread overview]
Message-ID: <4802FFB7.1060802@trash.net> (raw)
It appears your attempts to remove all warnings weren't entirely
successful, some of there even appear to be new (like all the
field precision warnings). It could also be the case that I simply
missed them previously in the noise, I'm not sure:
iptables.c: In function 'print_firewall':
iptables.c:741: warning: passing argument 1 of 'ipt_get_target' discards
qualifiers from pointer target type
iptables.c: In function 'print_firewall_line':
iptables.c:854: warning: passing argument 1 of 'ipt_get_target' discards
qualifiers from pointer target type
xtables.c: In function 'load_extension':
xtables.c:321: warning: field precision should have type 'int', but
argument 4 has type 'long int'
xtables.c:321: warning: field precision should have type 'int', but
argument 4 has type 'long int'
xtables.c:338: warning: field precision should have type 'int', but
argument 4 has type 'long int'
xtables.c:338: warning: field precision should have type 'int', but
argument 4 has type 'long int'
iptables-save.c: In function 'print_rule':
iptables-save.c:223: warning: passing argument 1 of 'ipt_get_target'
discards qualifiers from pointer target type
iptables.c: In function 'print_firewall':
iptables.c:741: warning: passing argument 1 of 'ipt_get_target' discards
qualifiers from pointer target type
iptables.c: In function 'print_firewall_line':
iptables.c:854: warning: passing argument 1 of 'ipt_get_target' discards
qualifiers from pointer target type
xtables.c: In function 'load_extension':
xtables.c:321: warning: field precision should have type 'int', but
argument 4 has type 'long int'
xtables.c:321: warning: field precision should have type 'int', but
argument 4 has type 'long int'
xtables.c:338: warning: field precision should have type 'int', but
argument 4 has type 'long int'
xtables.c:338: warning: field precision should have type 'int', but
argument 4 has type 'long int'
iptables-save.c: In function 'print_rule':
iptables-save.c:223: warning: passing argument 1 of 'ipt_get_target'
discards qualifiers from pointer target type
ip6tables.c: In function 'print_firewall':
ip6tables.c:741: warning: passing argument 1 of 'ip6t_get_target'
discards qualifiers from pointer target type
ip6tables.c: In function 'print_firewall_line':
ip6tables.c:851: warning: passing argument 1 of 'ip6t_get_target'
discards qualifiers from pointer target type
ip6tables-save.c: In function 'print_rule':
ip6tables-save.c:200: warning: passing argument 1 of 'ip6t_get_target'
discards qualifiers from pointer target type
ip6tables.c: In function 'print_firewall':
ip6tables.c:741: warning: passing argument 1 of 'ip6t_get_target'
discards qualifiers from pointer target type
ip6tables.c: In function 'print_firewall_line':
ip6tables.c:851: warning: passing argument 1 of 'ip6t_get_target'
discards qualifiers from pointer target type
xtables.c: In function 'load_extension':
xtables.c:321: warning: field precision should have type 'int', but
argument 4 has type 'long int'
xtables.c:321: warning: field precision should have type 'int', but
argument 4 has type 'long int'
xtables.c:338: warning: field precision should have type 'int', but
argument 4 has type 'long int'
xtables.c:338: warning: field precision should have type 'int', but
argument 4 has type 'long int'
ip6tables-save.c: In function 'print_rule':
ip6tables-save.c:200: warning: passing argument 1 of 'ip6t_get_target'
discards qualifiers from pointer target type
reply other threads:[~2008-04-14 6:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4802FFB7.1060802@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--cc=netfilter-devel@vger.kernel.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.