ODROID-N2: Missing kernel header

[krovetz]

The ODROID-N2 is a wonderful addition to ArchLinixArm. Thank you! Building an external module doesn't currently work due to missing headers.

$this->bbcode_second_pass_code('', 'n2> make
KMOD ko/enable_arm_pmu.ko
In file included from ./arch/arm64/include/asm/sysreg.h:25,
from ./arch/arm64/include/asm/cputype.h:108,
from ./arch/arm64/include/asm/cachetype.h:19,
from ./arch/arm64/include/asm/cache.h:19,
from ./include/linux/cache.h:5,
from ./include/linux/printk.h:8,
from ./include/linux/kernel.h:13,
from /home/krovetz/imac/tmp/enable_arm_pmu_v8/ko/enable_arm_pmu.c:4:
./arch/arm64/include/asm/opcodes.h:5:10: fatal error: ../../arm/include/asm/opcodes.h: No such file or directory
#include <../../arm/include/asm/opcodes.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
')

[karog]

Quite so. I posted the same thing a week ago regarding the linux-odroid-n2-headers package but did not know I should post it here. I wrote:

When I try to install wireguard-dkms, I get build errors for building the module because of missing files, namely:
$this->bbcode_second_pass_code('', '
build/arch/arm/include/asm/opcodes.h
build/arch/arm/include/asm/xen/hypervisor.h
build/drivers/amlogic/debug/irqflags_debug_arm64.h
')
I was able to find these specific files at https://github.com/hardkernel/linux/tree/odroidn2-4.9.y which is the URL for the package linux-odroid-n2-headers. There would appear to be a lot of other missing files as well in the alarm package.

What is the best way to get this package brought up to date?

[sjuut]

I have the same issue and for me, copying the files from the upstream repo to the 'missing' folders does not resolve the problem.

[karog]

The latest core/linux-odroid-n2-headers 4.9.180-1 added a number of the missing files.

However, the following dir is still missing almost all of its files:

build/drivers/amlogic/debug

In particular, as reported upthread, the package wireguard-dkms needs:

build/drivers/amlogic/debug/irqflags_debug_arm64.h

[krovetz]

A recent update to the kernel and headers appears to have fixed this for me. Thank you.