From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: /usr/include/linux/errno.h:1:23: fatal error: asm/errno.h: No such file or directory
Date: Sun, 16 Dec 2012 01:53:00 +0000 [thread overview]
Message-ID: <20121216015300.GA4939@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAAJw_ZsM+nWJc8nu7GiXrbOMftwwVvyYDczO6yBuCEGyoCrT8g@mail.gmail.com>
On Sun, Dec 16, 2012 at 09:39:01AM +0800, Jeff Chua wrote:
> On Sun, Dec 16, 2012 at 9:28 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > On Sun, Dec 16, 2012 at 09:23:38AM +0800, Jeff Chua wrote:
> >> How should the symbolic links be setup to compile the latest kernel?
> >>
> >>
> >> Currently I had these links and kernels compiled fine until 2 days ago.
> >>
> >> asm -> /usr/src/linux/include/uapi/asm-generic/
> >> asm-generic -> /usr/src/linux/include/uapi/asm-generic
> >> linux -> /usr/src/linux/include/uapi/linux
> >
> > What symlinks? /usr/include/* should not contain any symlinks into
> > the kernel source. At all.
>
> Al,
>
> Oh, perhaps I'm having the right setup. Where should I get the kernel
> headers.
>From your libc. Which ought to have its own copies, normally coming from
make headers_install in kernel source. And yes, it had been that way
for many years by now. Userland should *not* blindly grab the kernel
headers.
Incidentally, your 'asm' is obviously bogus - the headers that should end
up there ought to come from arch/<whatever>/include/uapi/asm (and _not_
by pointing a symlink to it); yours points to the place where asm-generic
ones ought to have been copied from.
next prev parent reply other threads:[~2012-12-16 1:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 1:23 /usr/include/linux/errno.h:1:23: fatal error: asm/errno.h: No such file or directory Jeff Chua
2012-12-16 1:28 ` Al Viro
2012-12-16 1:39 ` Jeff Chua
2012-12-16 1:40 ` Jeff Chua
2012-12-16 1:53 ` Al Viro [this message]
2012-12-16 2:06 ` Jeff Chua
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=20121216015300.GA4939@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jeff.chua.linux@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.