[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2l4mufrnhf6vka4cp7q5pcqphlk6b3gfd4m5c7yelczhubpwta@mkn2a7olzjh3>
Date: Wed, 18 Jun 2025 03:28:51 +0530
From: Brahmajit Das <listout@...tout.xyz>
To: Arnd Bergmann <arnd@...db.de>
Cc: linux-arm-kernel@...ts.infradead.org, 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 17.06.2025 23:36, Arnd Bergmann wrote:
> 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
That makes sense, its a crossdev[0] environment/compiler that I built.
I'll try adding -fno-freestanding.
[0]: https://wiki.gentoo.org/wiki/Crossdev
--
Regards,
listout
Powered by blists - more mailing lists