Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: building in 32bit chroot on x86_64 host broken - IGNORE
From:   Thomas Backlund <tmb@mageia.org>
To:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
CC:     Linus Torvalds <torvalds@linux-foundation.org>
References: <CA+55aFxhx_tKGm02UySguvbyfB_7oTF31QfgOHCK0YkBvmfV0g@mail.gmail.com>
 <8f46ed9a-85c0-8df4-2d1e-d268cbc9d0e9@mageia.org>
Message-ID: <48aa249f-22e8-924c-120c-8384eff9efb4@mageia.org>
Date:   Tue, 5 Jun 2018 21:11:01 +0259
MIME-Version: 1.0
In-Reply-To: <8f46ed9a-85c0-8df4-2d1e-d268cbc9d0e9@mageia.org>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Den 2018-06-05 kl. 20:52, skrev Thomas Backlund:
> 
> I have a 32bit x86 and a 64bit x86_64 install on the system.
> 
> With linux source up to 4.16.x I could do:
> 
> setarch i686 (or use command linux32)
> chroot /path/to/32bit/
> (/dev, /proc, /sys, /run is bind mounted in the chroot)
> 
> Then I could build a 32bit kernel in the chroot without booting the 
> 32bit system...
> 
> (host is running a 4.14 longterm kernel)
> 
> but building from 4.17 source in the chroot I get:
> 
> 
> $ uname -m
> i686
> $ make oldconfig
> scripts/kconfig/conf  --oldconfig Kconfig
> *
> * Restart config...
> *
> *
> * Linux/x86 4.17.0 Kernel Configuration
> *
> 64-bit kernel (64BIT) [Y/n/?] (NEW)
> 
> 
> 
> 
> So it does not pick up 32bit anymore ...
> 
> Is this intentional ? If so, why ? If not, how can I fix it ?
> 


Never mind...

For some reason I seem to have lost this  in the .config update to 4.17:

# CONFIG_64BIT is not set


Re-adding it restores proper behaviour...

Sorry for the noise...

--
Thomas