Public bug reported: gfs2-utils 3.6.1-2 fails to build from source in Ubuntu 26.10 (stonking) on arm64:
/usr/include/aarch64-linux-gnu/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'? Build log: https://launchpad.net/ubuntu/+source/gfs2-utils/3.6.1-2/+build/33821084 Root cause: gfs2-utils provides an internal compatibility header gfs2/include/linux/types.h which is exposed via -I compiler flags. When source files in gfs2/edit (extended.c, journal.c, hexedit.c) include <signal.h>, glibc's <bits/sigcontext.h> includes the kernel UAPI header <asm/sigcontext.h>, which in turn includes <linux/types.h>. Due to the include path order, the compiler includes the internal gfs2/include/linux/types.h instead of the system /usr/include/linux/types.h. The internal header only defines endian types (__le16 through __be64) and lacks the standard 128-bit kernel integer types (__s128 and __u128) used by arm64's struct fpsimd_context. Fix: Define __s128 and __u128 under #ifdef __SIZEOF_INT128__ in gfs2/include/linux/types.h to restore compatibility with arm64 kernel UAPI headers. ** Affects: gfs2-utils (Ubuntu) Importance: Undecided Status: New ** Tags: arm64 ftbfs gfs2-utils patch stonking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2170307 Title: gfs2-utils 3.6.1-2 FTBFS on arm64: unknown type name '__u128' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gfs2-utils/+bug/2170307/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
