[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAJw_ZuN-Spw5Ga+0EZiz1Oz0v1A5oz_O3_g9pUZr6Txe3wiNw@mail.gmail.com>
Date: Sun, 16 Dec 2012 09:40:11 +0800
From: Jeff Chua <jeff.chua.linux@...il.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: lkml <linux-kernel@...r.kernel.org>
Subject: Re: /usr/include/linux/errno.h:1:23: fatal error: asm/errno.h: No
such file or directory
On Sun, Dec 16, 2012 at 9:39 AM, Jeff Chua <jeff.chua.linux@...il.com> wrote:
> On Sun, Dec 16, 2012 at 9:28 AM, Al Viro <viro@...iv.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. After removing the links to the kernel source, here what I
> got ...
>
> make[1]: Nothing to be done for `all'.
> HOSTCC scripts/basic/fixdep
> In file included from /usr/include/bits/posix1_lim.h:160:0,
> from /usr/include/limits.h:144,
> from scripts/basic/fixdep.c:114:
> /usr/include/bits/local_lim.h:38:26: fatal error: linux/limits.h: No
> such file or directory
> compilation terminated.
> Oh, perhaps I'm having the right setup. Where should I get the kernel
NOT having the right setup.
Jeff.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists