From: Sasha Levin <sashal@kernel.org>
To: Max Krummenacher <max.oss.09@gmail.com>
Cc: Max Krummenacher <max.krummenacher@toradex.com>,
Ian Rogers <irogers@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Subject: Re: 6.1.159-rc1 regression on building perf
Date: Mon, 17 Nov 2025 11:27:02 -0500 [thread overview]
Message-ID: <aRtM1qdOprtHrw4n@laps> (raw)
In-Reply-To: <CAEHkU3Vr4RVG1Up1_cnoV70QRaYrRXW8ONCMOBB88F+Cu7WRuw@mail.gmail.com>
On Mon, Nov 17, 2025 at 05:00:39PM +0100, Max Krummenacher wrote:
>Hi
>
>Our CI found a regression when cross-compiling perf from the 6.1.159-rc1
>sources in a yocto setup for a arm64 based machine.
>
>In file included from .../tools/include/linux/bitmap.h:6,
> from util/pmu.h:5,
> from builtin-list.c:14:
>.../tools/include/asm-generic/bitsperlong.h:14:2: error: #error
>Inconsistent word size. Check asm/bitsperlong.h
> 14 | #error Inconsistent word size. Check asm/bitsperlong.h
> | ^~~~~
>
>
>I could reproduce this as follows in a simpler setup:
>
>git clone -b linux-6.1.y
>https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>cd linux-stable-rc/
>export ARCH=arm64
>export CROSS_COMPILE=aarch64-none-linux-gnu-
>make defconfig
>make -j$(nproc)
>cd tools/perf
>make
>
>Reverting commit 4d99bf5f8f74 ("tools bitmap: Add missing
>asm-generic/bitsperlong.h include") fixed the build in my setup however
>I think that the issue the commit addresses would then reappear, so I
>don't know what would be a good way forward.
Thanks for the report! I could reproduce this issue localy.
Could you please try cherry-picking commit 8386f58f8deda on top and seeing if
it solves the issue and your CI passes?
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-11-17 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 16:00 6.1.159-rc1 regression on building perf Max Krummenacher
2025-11-17 16:27 ` Sasha Levin [this message]
2025-11-17 17:00 ` Max Krummenacher
2025-11-17 18:59 ` Sasha Levin
2025-11-17 16:27 ` Ian Rogers
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=aRtM1qdOprtHrw4n@laps \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=irogers@google.com \
--cc=max.krummenacher@toradex.com \
--cc=max.oss.09@gmail.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.