linux-kernel - Re: Failing to build mainline kernel for arm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <2fb06649-f2e7-4ad1-a831-f8b6b0dbafee@app.fastmail.com>
Date: Tue, 17 Jun 2025 23:36:15 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Brahmajit Das" <listout@...tout.xyz>,
 linux-arm-kernel@...ts.infradead.org
Cc: linux-kernel@...r.kernel.org, "Russell King" <linux@...linux.org.uk>,
 "Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: Failing to build mainline kernel for arm

On Tue, Jun 17, 2025, at 23:23, Brahmajit Das wrote:
> Hello developers,
>
> I was trying to build the mainline kernel (top commit
> 4663747812d1a272312d1b95cbd128f0cdb329f2) and came across a build
> failure with allyesconfig.
>
> $ make ARCH=arm CROSS_COMPILE=arm-none-eabi-

The problem is likely that you use a baremetal toolchain, rather
than an arm-linux-gnueabi or arm-linux-gnueabihi toolchain.

There is some logic that tries to decide if uint32_t should
be 'unsigned int' or 'unsigned long' based on included headers,
and it seems that your compiler comes to a different conclusion
here.

If this is a freestanding compiler, can you try adding
-fno-freestanding to the cflags?

     Arnd