Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Nicolas Schier <nsc@kernel.org>
To: Andrew Valencia <andy@linux486.org>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Kconfig olddefconfig nukes 32-bit
Date: Sun, 12 Apr 2026 18:19:54 +0200	[thread overview]
Message-ID: <advGKvtLfEb1vwNK@levanger> (raw)
In-Reply-To: <af3a3eea-ae34-4f94-b17c-43f154e80ff7@app.fastmail.com>

Cc: linux-kbuild

On Sat, Apr 11, 2026 at 10:55:15AM -0700, Andrew Valencia wrote:
> Hi,
> 
> I'm working over in the 6.19..12 world, and brought over a working
> .config which I updated with olddefconfig.  Long story short, the
> config was converted to a x86 64-bit config.
> 
> The issue is the new config entry 64BIT, which has a default value of
> ARCH != "i386".

yes, there is a 64BIT Kconfig symbol defined at arch/x86/Kconfig which
is true by default for non-i386 builds.  According to my git tree, the
corresponding lines did not change since v4.18 [1].

[1]: https://git.kernel.org/kbuild/c/104daea149c45

> On my 32-bit x86 build machine with its 32-bit .config, the default Y
> is being selected.  Is it possible i386 is not the correct name for
> ARCH on this target?

I guess, that you want to cross-build a 32bit-Linux on a 64bit-machine,
right?  How did you call olddefconfig (e.g. make ARCH=i386 olddefconfig)?

Kind regards

-- 
Nicolas

       reply	other threads:[~2026-04-12 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <af3a3eea-ae34-4f94-b17c-43f154e80ff7@app.fastmail.com>
2026-04-12 16:19 ` Nicolas Schier [this message]
2026-04-12 18:36   ` Kconfig olddefconfig nukes 32-bit Andrew Valencia
2026-04-14  9:40     ` Nicolas Schier
2026-04-14 10:04       ` Nicolas Schier
2026-05-05 23:49         ` Andrew Valencia

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=advGKvtLfEb1vwNK@levanger \
    --to=nsc@kernel.org \
    --cc=andy@linux486.org \
    --cc=linux-kbuild@vger.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