I think this is a bug in linux-libc-dev, not in palo. The linux-libc-dev -provided /usr/include/linux/elf.h declares functions that take an loff_t * as an argument, and loff_t is defined in /usr/include/linux/types.h *only* when __KERNEL_STRICT_NAMES is undefined. But __KERNEL_STRICT_NAMES must be defined for palo to avoid conflicts with other userspace type definitions. linux/elf.h should be usable even when __KERNEL_STRICT_NAMES is set; loff_t should be replaced with __kernel_loff_t in this header.
As a workaround for palo though, palo can include the userspace sys/types.h before linux/elf.h.
I think this is a bug in linux-libc-dev, not in palo. The linux-libc-dev -provided /usr/include/ linux/elf. h declares functions that take an loff_t * as an argument, and loff_t is defined in /usr/include/ linux/types. h *only* when __KERNEL_ STRICT_ NAMES is undefined. But __KERNEL_ STRICT_ NAMES must be defined for palo to avoid conflicts with other userspace type definitions. linux/elf.h should be usable even when __KERNEL_ STRICT_ NAMES is set; loff_t should be replaced with __kernel_loff_t in this header.
As a workaround for palo though, palo can include the userspace sys/types.h before linux/elf.h.