All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: netfilter-devel@lists.netfilter.org,
	Patrick McHardy <kaber@trash.net>,
	Colin Harrison <colin.harrison@virgin.net>
Subject: Re: Unable to build iptables on linux kernel 2.6.10 + 2.6.11-rc2 +	2.6.11-rc2-bk5
Date: Tue, 01 Feb 2005 02:31:17 +0100	[thread overview]
Message-ID: <41FEDBE5.3030606@eurodev.net> (raw)
In-Reply-To: <20050201005133.GJ31837@postel.suug.ch>

Thomas Graf wrote:

>> 		/* The protocol. */
>>-		u8 protonum;
>>+		u_int8_t protonum;
>> 
>> 		/* The direction (for tuplehash) */
>>-		u8 dir;
>>+		u_int8_t dir;
>>    
>>
>
>I think __u8 would be a better choice.
>  
>

I don't think so. With __u8 iptables doesn't compile anymore on my laptop.

cc -O2 -Wall -Wunused -I/home/pablo/bk/linux-2.5/include -Iinclude/ 
-DIPTABLES_VERSION=\"1.3.0\"  -fPIC -o extensions/libipt_conntrack_sh.o 
-c extensions/libipt_conntrack.c
In file included from extensions/libipt_conntrack.c:13:
/home/pablo/bk/linux-2.5/include/linux/netfilter_ipv4/ip_conntrack_tuple.h:67: 
parse error before `__u8'
/home/pablo/bk/linux-2.5/include/linux/netfilter_ipv4/ip_conntrack_tuple.h:67: 
warning: no semicolon at end of struct or union
...

--
Pablo

  reply	other threads:[~2005-02-01  1:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 15:53 Unable to build iptables on linux kernel 2.6.10 + 2.6.11-rc2 + 2.6.11-rc2-bk5 Colin Harrison
2005-01-30 22:27 ` Pablo Neira
2005-02-01  0:51   ` Thomas Graf
2005-02-01  1:31     ` Pablo Neira [this message]
2005-02-01  7:04     ` Tomáš Macek
2005-02-01 13:17     ` Patrick McHardy
2005-02-01 13:17   ` Patrick McHardy

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=41FEDBE5.3030606@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=colin.harrison@virgin.net \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=tgraf@suug.ch \
    /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.