From: Alexey Dobriyan <adobriyan@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: daniel.diaz@linaro.org, linux-kernel@vger.kernel.org,
rdunlap@infradead.org, sedat.dilek@gmail.com
Subject: make defconfig (Re: + x86-defconfigs-explicitly-unset-config_64bit-in-i386_defconfig.patch added to -mm tree)
Date: Fri, 21 Aug 2020 20:22:31 +0300 [thread overview]
Message-ID: <20200821172231.GA1444408@localhost.localdomain> (raw)
In-Reply-To: <20200820212940.Kq1ky-JHH%akpm@linux-foundation.org>
On Thu, Aug 20, 2020 at 02:29:40PM -0700, akpm@linux-foundation.org wrote:
> Subject: x86/defconfigs: Explicitly unset CONFIG_64BIT in i386_defconfig
>
> A recent refresh of the defconfigs got rid of the following (unset)
> config:
>
> # CONFIG_64BIT is not set
>
> Innocuous as it seems, when the config file is saved again the
> behavior is changed so that CONFIG_64BIT=y.
>
> Currently,
>
> $ make i386_defconfig
> $ grep CONFIG_64BIT .config
> CONFIG_64BIT=y
>
> whereas previously (and with this patch):
>
> $ make i386_defconfig
> $ grep CONFIG_64BIT .config
> # CONFIG_64BIT is not set
It is highly, highly, highly advisable to always pass ARCH when dealing
with 32/64-bit archs:
+---------------------------------------+
| make ARCH=x86_64 defconfig |
| make ARCH=i386 defconfig |
+---------------------------------------+
The reason is that long ago ARCH was deduced from bitness of the system
make was run on, so that
make allnoconfig
gave 32-bit config on 32-but system and 64-bit on 64-bit system which is
natural thing to do.
During i386/x86_64 merge CONFIG_64BIT became user visible option!
" make allnoconfig" started giving 32-bit config even on x86_64 and 64-bit
defconfig and allmodconfig which it does to this day.
Always passing ARCH is the only way to maintain sanity. I have shell
alias to always pass ARCH=x86_64 so that bitness is both deterministic
and can be overridden.
next parent reply other threads:[~2020-08-21 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200820212940.Kq1ky-JHH%akpm@linux-foundation.org>
2020-08-21 17:22 ` Alexey Dobriyan [this message]
2020-08-21 17:27 ` make defconfig (Re: + x86-defconfigs-explicitly-unset-config_64bit-in-i386_defconfig.patch added to -mm tree) Randy Dunlap
2020-08-21 18:52 ` Sedat Dilek
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=20200821172231.GA1444408@localhost.localdomain \
--to=adobriyan@gmail.com \
--cc=daniel.diaz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sedat.dilek@gmail.com \
/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