[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200908134350.GX1891694@smile.fi.intel.com>
Date: Tue, 8 Sep 2020 16:43:50 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
linux-kernel@...r.kernel.org,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Tony Luck <tony.luck@...el.com>
Subject: Re: [PATCH v1] x86/defconfigs: Unbreak 32-bit defconfig builds
On Tue, Sep 08, 2020 at 02:13:54PM +0200, Ingo Molnar wrote:
>
> * Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
>
> > After the commit 1d0e12fd3a84 ("x86/defconfigs: Refresh defconfig files")
> > 32-bit builds using defconfig become broken because on x86_64 build host
> > with no ARCH provided the default behaviour is to assume 64-bit independently
> > on the configuration file name. The crucial part is CONFIG_64BIT option
> > that used to be explicit. Let restore the latter option in order to unbreak
> > 32-bit builds.
>
> So exactly which build method broke due to this? The typical way to do a defconfig build is:
>
> make ARCH=i386 defconfig
>
> which still works fine AFAICS.
uname => x86_64
make i386_defconfig
It was very convenient to not supply ARCH when build on multi-arch host.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists