Manuel Gonzalez Montoya wrote:
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.
For me the last 2 lines (312 & 313 ) from
arch/x86/include/generated/uapi/asm/unistd_64.h looks like this
when openned in vim
312 #define __NR_setns 308
313 #def^@^@^@^@^@^@^@^@
Then this is your problem. unistd_64.h is not being generated properly.
Try, in a clean envronment, 'make V=1' to see how unistd_64.h is being
generated and investigate from there.
For me, unistd_64.h has 334 lines ending with:
#define __NR_sendmmsg 307
#define __NR_setns 308
#define __NR_getcpu 309
#define __NR_process_vm_readv 310
#define __NR_process_vm_writev 311
#define __NR_kcmp 312
#define __NR_finit_module 313
#define __NR_sched_setattr 314
#define __NR_sched_getattr 315
#define __NR_renameat2 316
#define __NR_seccomp 317
#define __NR_getrandom 318
#define __NR_memfd_create 319
#define __NR_kexec_file_load 320
#define __NR_bpf 321
#define __NR_execveat 322
#define __NR_userfaultfd 323
#define __NR_membarrier 324
#define __NR_mlock2 325
#define __NR_copy_file_range 326
#define __NR_preadv2 327
#define __NR_pwritev2 328
#endif /* _ASM_X86_UNISTD_64_H */
-- 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
