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
| ||
|
Date: Wed, 20 Oct 2021 07:23:42 -0700 From: Randy Dunlap <rdunlap@...radead.org> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>, Linux Next Mailing List <linux-next@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>, "linux-um@...ts.infradead.org" <linux-um@...ts.infradead.org>, Alex Gaynor <alex.gaynor@...il.com>, Geoffrey Thomas <geofft@...reload.com>, Finn Behrens <me@...enk.de>, Adam Bratschi-Kaye <ark.email@...il.com>, Wedson Almeida Filho <wedsonaf@...gle.com>, Boqun Feng <boqun.feng@...il.com>, Sumera Priyadarsini <sylphrenadin@...il.com>, Michael Ellerman <mpe@...erman.id.au>, Sven Van Asbroeck <thesven73@...il.com>, Gary Guo <gary@...yguo.net>, Boris-Chengbiao Zhou <bobo1239@....de>, Fox Chen <foxhlchen@...il.com>, Ayaan Zaidi <zaidi.ayaan@...il.com>, Douglas Su <d0u9.su@...look.com>, Yuki Okushi <jtitor@...6.org> Subject: Re: linux-next: Tree for Oct 18 ('make' error on ARCH=um) On 10/19/21 9:56 PM, Stephen Rothwell wrote: > Hi Randy, > > On Tue, 19 Oct 2021 00:18:44 +0200 Miguel Ojeda <miguel.ojeda.sandonis@...il.com> wrote: >> >> On Mon, Oct 18, 2021 at 11:58 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote: >>> >>> In commit >>> >>> c862c7fee526 ("Kbuild: add Rust support") >>> >>> from the rust tree, these bits should probably not be there: >>> >>> -ifneq ($(findstring clang,$(CC_VERSION_TEXT)),) >>> include $(srctree)/scripts/Makefile.clang >>> -endif >> >> So this was on purpose -- we need the Clang flags even in GCC builds >> for bindgen. But now there is that `$(error ...)` added there :( >> >>> Miguel, does that seem reasonable? >> >> Of course, for today please feel free to apply your fix (i.e. to put >> the conditional back to where it was). I will solve it on my side >> tomorrow. > > Can you please check that this is fixed for you after I do the release > today? > I will. It's part of my nightly cron job. -- ~Randy
Powered by blists - more mailing lists