From: Adrian Bunk <bunk@stusta.de>
To: Andrew Walrond <andrew@walrond.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: Kernel headers - linux-atm userspace build broken by recent change; __be16 undefined
Date: Fri, 19 Jan 2007 15:37:25 +0100 [thread overview]
Message-ID: <20070119143724.GN9093@stusta.de> (raw)
In-Reply-To: <45AFE52C.30308@walrond.org>
On Thu, Jan 18, 2007 at 09:22:52PM +0000, Andrew Walrond wrote:
> Don't know exactly when this change went in, but it's not in 2.6.18.3
> and is in 2.6.19.2+
>
> $ diff linux/include/linux/if_arp.h linux-2.6/include/linux/if_arp.h
> 133,134c133,134
> < unsigned short ar_hrd; /* format of hardware address */
> < unsigned short ar_pro; /* format of protocol address */
> ---
> > __be16 ar_hrd; /* format of hardware address */
> > __be16 ar_pro; /* format of protocol address */
> 137c137
> < unsigned short ar_op; /* ARP opcode (command) */
> ---
> > __be16 ar_op; /* ARP opcode (command) */
>
>
> This causes the linux-atm userspace compile to fail like this:
>
> In file included from arp.c:19:
> /usr/include/linux/if_arp.h:133: error: expected
> specifier-qualifier-list before '__be16'
>
> I guess if_arp.h needs to include include/linux/byteorder/big_endian.h?
No, linux/types.h
But what bothers me more about if_arp.h is that it is one of the
headers using "struct sockaddr" in userspace, but as far as I can see we
aren't exporting it in any header.
This seems to work since glibc is providing the struct, but this looks
a bit fishy.
> Andrew Walrond
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
parent reply other threads:[~2007-01-19 14:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <45AFE52C.30308@walrond.org>]
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=20070119143724.GN9093@stusta.de \
--to=bunk@stusta.de \
--cc=andrew@walrond.org \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).