[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whddBhfi5DUi370W3pYs+z3r2E7KYuHjwR=a1eRig5Gxg@mail.gmail.com>
Date: Sat, 25 Jan 2025 14:09:16 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andrew Morton <akpm@...ux-foundation.org>, Uros Bizjak <ubizjak@...il.com>
Cc: linux-mm@...ck.org, mm-commits@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] MM updates for 6.14-rc1
On Fri, 24 Jan 2025 at 16:22, Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> Linus, please merge the MM updates for the 6.14 development cycle,
This does not build at all for me.
I get
./arch/x86/include/asm/current.h:49:9: error: call to undeclared
function '__typeof_unqual__'; ISO C99 and later do not support
implicit function declarations [-Wimplicit-function-declaration]
when running the Rust 'bindgen', and what seems to be going on is that
my version of *gcc* does support __typeof_unqual__, so I end up with
CONFIG_CC_HAS_TYPEOF_UNQUAL=y
in my kernel config, but I think that 'bindgen' that generates the
Rust bindings is based on LLVM, and clearly does not understand
__typeof_unqual__.
I have bindgen 0.69.5 (plain F40 install), in case somebody wants to test.
Apparently few people test linux-next with Rust enabled, and the
reports that I find on lkml were ignored.
I do see reports of this failure on lkml from mid-December, so it's
not like I'm the first person ever to see this.
Anyway, pulled and then unpulled again.
Linus
Powered by blists - more mailing lists