From: Mike Galbraith <efault@gmx.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.18-rc6-mm1 breaks glibc build
Date: Sat, 09 Sep 2006 14:25:06 +0000 [thread overview]
Message-ID: <1157811906.10627.3.camel@Homer.simpson.net> (raw)
In-Reply-To: <1157802554.2977.79.camel@pmac.infradead.org>
On Sat, 2006-09-09 at 12:49 +0100, David Woodhouse wrote:
> On Sat, 2006-09-09 at 13:44 +0000, Mike Galbraith wrote:
> > /lib/modules/2.6.18-rc6-mm1-smp/build/include/linux/err.h: Assembler messages:
>
> Don't care. <linux/err.h> is not a header which is exported to userspace
> by 'make headers_install'. No userspace build, including glibc, should
> ever be able to see it.
I kinda figured that was going to be the answer, but not knowing why
glibc was doing that, I thought it was worth a mention. Thanks.
-Mike
prev parent reply other threads:[~2006-09-09 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 13:44 Mike Galbraith
2006-09-09 11:49 ` David Woodhouse
2006-09-09 14:25 ` Mike Galbraith [this message]
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=1157811906.10627.3.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.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
all inboxes | Powered by JetHome®