[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiS0rpOSRyh-8hOQm3yT3q_JkLgQj0ur9QuyUKxWU2sdQ@mail.gmail.com>
Date: Sat, 10 Sep 2022 13:28:50 -0400
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>,
Nathan Chancellor <nathan@...nel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Will Deacon <will@...nel.org>,
Waiman Long <longman@...hat.com>,
Boqun Feng <boqun.feng@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: [PATCH] x86/config: Make the x86 defconfigs a bit more usable
On Fri, Sep 9, 2022 at 6:05 PM Masahiro Yamada <masahiroy@...nel.org> wrote:
>
> If you do not like the inconsistency,
> the support for ARCH=i386 and ARCH=x86_64 must be removed.
Is there any sane alternative for "do cross-architecture test builds"?
I do things like "make ARCH=i386 allmodconfig" myself, and I have to
admit that it's annoying that you have to then remember to do "make
ARCH=ii386" to do the actual build too, because otherwise Kcoinfig
will mess up the architecture, because it didn't make it into the
final simplified .config.
This is probably more noticeable with "defconfig" because then the
"ARCH=xyz" part has *other* effects too (ie it is also what says
*which* defconfig to pick).
So this is a bit of an annoyance, in that it's not trivial to just
"make the config for ARCH xyz" and then "make".
Linus
Powered by blists - more mailing lists