Re: [Buildroot] [PATCH] package/lldpd: fix compilation issue with kernel 7.3 on aarch64

From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thibaut Collet <thbt.cllt@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/lldpd: fix compilation issue with kernel 7.3 on aarch64
Date: Mon, 28 Sep 2026 23:27:15 +0200	[thread overview]
Message-ID: <arrbTcuJn4IUQQvT@windsurf> (raw)
In-Reply-To: <20260928152218.94978-1-thbt.cllt@gmail.com>

Hello Thibault,

On Mon, Sep 28, 2026 at 05:22:18PM +0200, Thibaut Collet wrote:
> lldpd bundles some uapi linux files for old distributions, especially
> the types.h one.
> 
> Since kernel commit d4bf9e08d412 ("arm64: uapi: Use __u128 instead of
> __uint128_t in UAPI headers"), the type __u128 is used by sigcontext.h.
> This type is defined in types.h, but the old version bundled by lldpd
> does not provide it. This lack leads to the following compilation error:
> 
>   In file included from ../../../../host/aarch64-buildroot-linux-gnu/sysroot/usr/include/bits/sigcontext.h:30,
>                    from ../../../../host/aarch64-buildroot-linux-gnu/sysroot/usr/include/signal.h:301,
>                    from ../../../../host/aarch64-buildroot-linux-gnu/sysroot/usr/include/sys/param.h:28,
>                    from privsep_io.c:5:
>   ../../../../host/aarch64-buildroot-linux-gnu/sysroot/usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
>      81 |         __u128 vregs[32];
>         |         ^~~~~~
>         |         __u32
> 
> As Buildroot is not an old distribution and always provides the uapi
> linux files, the lldpd ones are removed at the post patch step to have
> a consistent set of uapi include files.
> 
> Signed-off-by: Thibaut Collet <thbt.cllt@gmail.com>

Thanks for the patch!

However, when you say "Buildroot is not an old distribution and always
provides the uapi linux files": we do allow building with fairly old
kernels. So which version of the kernel header does lldpd now requires
after your change? I'm interested to understand what is the chance of
this patch breaking some other users that are running old kernels.

Thanks for your feedback!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot