From: Harvey Harrison <harvey.harrison@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: bluebird@gentoo.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Compiling glibc with 2.6.28 linux headers
Date: Tue, 16 Dec 2008 17:22:26 -0800 [thread overview]
Message-ID: <1229476946.6481.0.camel@brick> (raw)
In-Reply-To: <20081216.011334.124918024.davem@davemloft.net>
On Tue, 2008-12-16 at 01:13 -0800, David Miller wrote:
> From: Friedrich Oslage <bluebird@gentoo.org>
> Date: Sat, 13 Dec 2008 16:55:02 +0100
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi,
> >
> > when compiling glibc(2.9, 20081208 snapshot) with linux 2.6.28-rc8
> > headers I get a lot of errors like this one:
> >
> > In file included from
> > /tmp/toolchain-build/rootfs/usr/include/asm/byteorder.h:49,
> > from
> > /tmp/toolchain-build/rootfs/usr/include/linux/atalk.h:4,
> > from ../sysdeps/unix/sysv/linux/netatalk/at.h:25,
> > from ../sysdeps/unix/sysv/linux/sa_len.c:22:
> > /tmp/toolchain-build/rootfs/usr/include/linux/byteorder.h:8:3: error:
> > #error Fix asm/byteorder.h to define one endianness
>
> Harvey, we might need to do something about this.
I'm on the run today, will take a look in 24 hours.
Harvey
next prev parent reply other threads:[~2008-12-17 1:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4943DAD6.7070402@gentoo.org>
2008-12-16 9:13 ` Compiling glibc with 2.6.28 linux headers David Miller
2008-12-17 1:22 ` Harvey Harrison [this message]
2008-12-18 1:46 ` [PATCH-2.6.28 final] byteorder: fix new headers for userspace Harvey Harrison
2008-12-18 20:09 ` Linus Torvalds
2008-12-18 20:47 ` Linus Torvalds
2008-12-18 20:53 ` Harvey Harrison
2008-12-19 8:08 ` Arjan van de Ven
2008-12-19 16:37 ` Harvey Harrison
2009-01-06 10:23 ` Gerd Hoffmann
2009-01-06 16:41 ` Harvey Harrison
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=1229476946.6481.0.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=bluebird@gentoo.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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