From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH v1] x86/defconfigs: Unbreak 32-bit defconfig builds
Date: Tue, 8 Sep 2020 16:49:18 +0300 [thread overview]
Message-ID: <7424b868-7463-2ea4-1cb0-386b143dc8f0@linux.intel.com> (raw)
In-Reply-To: <20200908121354.GA3848343@gmail.com>
Hi
On 9/8/20 3:13 PM, Ingo Molnar wrote:
>
> * Andy Shevchenko <andriy.shevchenko@linux.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.
>
Maybe wrong way to do it, just plain "make i386_defconfig". I'm aware of
ARCH=, but never needed to specify it for x86 targets.
Jarkko
next prev parent reply other threads:[~2020-09-08 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 10:00 Andy Shevchenko
2020-09-08 12:13 ` Ingo Molnar
2020-09-08 13:43 ` Andy Shevchenko
2020-09-09 8:00 ` Ingo Molnar
2020-09-09 10:14 ` Andy Shevchenko
2020-09-08 13:49 ` Jarkko Nikula [this message]
2020-09-08 17:50 ` Randy Dunlap
2020-09-08 18:45 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7424b868-7463-2ea4-1cb0-386b143dc8f0@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome