Manuel Gonzalez Montoya wrote:
I have always used root to compile/install when upgrading the kernel without a
problem, but today I tried the compilation part as a normal user and it failed
with the following error:


In file included from ./arch/x86/include/asm/unistd.h:23:0,
                  from ./arch/x86/include/asm/seccomp.h:4,
                  from ./include/linux/seccomp.h:11,
                  from ./include/linux/sched.h:43,
                  from ./include/linux/kasan.h:4,
                  from ./include/linux/slab.h:118,
                  from ./include/linux/crypto.h:24,
                  from arch/x86/kernel/asm-offsets.c:8:
./arch/x86/include/generated/uapi/asm/unistd_64.h:313:2: error:
invalid preprocessing directive #def
  #def

steps to reproduce:

wget -c https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.8.4.tar.xz
tar -xf linux-4.8.4.tar.xz
cd linux-4.8.4
make mrproper
cp /boot/config-4.8.1 .config
make oldconfig
make

What could be the problem ?.
any help is welcome.

Curious problem. I did the same steps as you and had no problem. One minor difference was that my config was slightly older (4.7.2), but I wouldn't think that would make any difference.

I assume you are using the latest gcc:

$ gcc --version
gcc (GCC) 6.2.0

Also, did you do 'rm -rf linux-4.8.4' before you extracted the source? The make mrproper *should* fix that it you didn't, but if there are remnants owned by root, then it could cause a problem.

Also, arch/x86/include/generated/uapi/asm/unistd_64.h line 313 for me is:

#define __NR_getcpu 309

Since that appears to be a generated file, it looks like it wasn't generated properly.

  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Reply via email to