From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Viktor Malik <vmalik@redhat.com>,
Andrii Nakryiko <andrii@kernel.org>, Daniel Xu <dxu@dxuuu.xyz>,
Alexei Starovoitov <ast@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
ncopa@alpinelinux.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Stable <stable@vger.kernel.org>
Subject: Fwd: stable kernels 6.6.23 and 6.1.83 fails to build: error: unknown type name 'u32'
Date: Mon, 1 Apr 2024 21:09:55 +0700 [thread overview]
Message-ID: <ZgrAM4NjZQWZ2Jq6@archie.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 2931 bytes --]
Hi,
On Bugzilla, ncopa@alpinelinux.org reported resolve_btfids FTBFS regression
on musl system [1]:
> The latest releases fails to build with musl libc (Alpine Linux edge and v3.19):
>
> ```
> rm -f -f /home/ncopa/aports/main/linux-lts/src/build-lts.x86_64/tools/bpf/resolve_btfids/libbpf/libbpf.a; ar rcs /home/ncopa/aports/main/linux-lts/src/build-lts.x86_64/tool
> s/bpf/resolve_btfids/libbpf/libbpf.a /home/ncopa/aports/main/linux-lts/src/build-lts.x86_64/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf-in.o
> In file included from main.c:73:
> /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:7:9: error: unknown type name 'u32'
> 7 | u32 cnt;
> | ^~~
> /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:8:9: error: unknown type name 'u32'
> 8 | u32 ids[];
> | ^~~
> /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:12:9: error: unknown type name 'u32'
> 12 | u32 cnt;
> | ^~~
> /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:13:9: error: unknown type name 'u32'
> 13 | u32 flags;
> | ^~~
> /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:15:17: error: unknown type name 'u32'
> 15 | u32 id;
> | ^~~
> /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:16:17: error: unknown type name 'u32'
> 16 | u32 flags;
> | ^~~
> /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:215:8: error: unknown type name 'u32'
> 215 | extern u32 btf_tracing_ids[];
> | ^~~
> make[4]: *** [/home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/build/Makefile.build:98: /home/ncopa/aports/main/linux-lts/src/build-lts.x86_64/tools/bpf/resolve_btfids
> /main.o] Error 1
> make[4]: *** Waiting for unfinished jobs....
> make[3]: *** [Makefile:83: /home/ncopa/aports/main/linux-lts/src/build-lts.x86_64/tools/bpf/resolve_btfids//resolve_btfids-in.o] Error 2
> make[2]: *** [Makefile:76: bpf/resolve_btfids] Error 2
> make[1]: *** [/home/ncopa/aports/main/linux-lts/src/linux-6.6/Makefile:1354: tools/bpf/resolve_btfids] Error 2
> make: *** [/home/ncopa/aports/main/linux-lts/src/linux-6.6/Makefile:234: __sub-make] Error 2
> ```
Bisection led to upstream commit 9707ac4fe2f5ba ("tools/resolve_btfids:
Refactor set sorting with types from btf_ids.h") as the culprit.
See the report on Bugzilla for the full thread and proposed fix.
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=218647
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2024-04-01 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 14:09 Bagas Sanjaya [this message]
2024-04-01 14:15 ` Fwd: stable kernels 6.6.23 and 6.1.83 fails to build: error: unknown type name 'u32' Greg KH
2024-04-01 14:26 ` Bagas Sanjaya
2024-04-01 14:36 ` Greg Thelen
2024-04-01 15:27 ` Natanael Copa
2024-04-01 15:09 ` Fwd: " Alexei Starovoitov
2024-04-01 15:24 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZgrAM4NjZQWZ2Jq6@archie.me \
--to=bagasdotme@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=linux-kernel@vger.kernel.org \
--cc=ncopa@alpinelinux.org \
--cc=ndesaulniers@google.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=vmalik@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).