From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.28 headers break kbd and net-tools userspace builds
Date: Thu, 22 Jan 2009 19:04:38 +0000 [thread overview]
Message-ID: <4978C346.9070504@walrond.org> (raw)
In-Reply-To: <20090122175645.GA14178@uranus.ravnborg.org>
Sam Ravnborg wrote:
>
> I checked the include guards and they are correct.
>
> Could you please investige where it picks up the first definition
> of struct iphdr.
>
>
Here you go:
$ make iptunnel.o
cc -D_GNU_SOURCE -O2 -Wall -g -I. -idirafter ./include/ -Ilib -c -o
iptunnel.o iptunnel.c
In file included from /usr/include/linux/if_tunnel.h:5,
from iptunnel.c:39:
/usr/include/linux/ip.h:85: error: redefinition of 'struct iphdr'
$ grep -r iphdr /usr/include/
/usr/include/netinet/ip.h:struct iphdr
/usr/include/netinet/tcp.h: * This should be defined as MIN(512, IP_MSS
- sizeof (struct tcpiphdr)).
/usr/include/linux/if_tunnel.h: struct iphdr iph;
/usr/include/linux/ip.h:struct iphdr {
$ grep netinet/ip.h iptunnel.c
#include <netinet/ip.h>
So linux/ip.h is clashing with glibc(2.8)'s netinet/ip.h
Andrew Walrond
next prev parent reply other threads:[~2009-01-22 19:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 12:45 2.6.28 headers break kbd and net-tools userspace builds Andrew Walrond
2009-01-22 17:56 ` Sam Ravnborg
2009-01-22 19:04 ` Andrew Walrond [this message]
[not found] ` <4978C301.1040705@walrond.org>
2009-01-22 19:12 ` Sam Ravnborg
2009-01-27 5:08 ` David Miller
2009-01-27 10:44 ` Jan Engelhardt
2009-01-28 20:29 ` David Miller
2009-01-30 4:12 ` Jan Engelhardt
2009-02-02 10:35 ` Andrew Walrond
2009-02-02 20:05 ` David Miller
2009-02-02 21:13 ` Andrew Walrond
2009-02-02 21:24 ` David Miller
2009-02-02 21:27 ` David Miller
2009-02-03 4:58 ` Sam Ravnborg
2009-02-03 5:26 ` David Miller
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=4978C346.9070504@walrond.org \
--to=andrew@walrond.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox