From: Sean MacLennan <smaclennan@pikatech.com>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Big include file move breaks user mode
Date: Wed, 6 Aug 2008 11:01:24 -0400 [thread overview]
Message-ID: <20080806110124.40280d13@lappy.seanm.ca> (raw)
In-Reply-To: <200808061651.40361.arnd@arndb.de>
On Wed, 6 Aug 2008 16:51:40 +0200
"Arnd Bergmann" <arnd@arndb.de> wrote:
> The user space headers are provided by your distribution, not
> by the kernel, so include/asm should be a directory, not a symlink.
> If you are building your own distro, don't just copy the files
> but rather use 'make headers_install' to get a sanitized version.
Sorry, I forgot to reply to the list :( Kumar mentioned the "make
headers_install" and I got it working with our build system. So
everything is back on track.
Cheers,
Sean
next prev parent reply other threads:[~2008-08-06 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 16:09 Big include file move breaks user mode Sean MacLennan
2008-08-05 16:13 ` Kumar Gala
2008-08-06 14:51 ` Arnd Bergmann
2008-08-06 15:01 ` Sean MacLennan [this message]
2008-08-06 17:43 ` René Rebe
2008-08-06 17:44 ` René Rebe
2008-08-06 19:21 ` Kumar Gala
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=20080806110124.40280d13@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).