Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp1277979imm; Tue, 5 Jun 2018 11:51:24 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLaNzrQkcrw3HD8hMyxYvP/5AuPSsrZXdIWB9PuhCnndKYKJG5HbjMsiYu+E5R41Bz50tM1 X-Received: by 2002:a17:902:422:: with SMTP id 31-v6mr28391161ple.320.1528224683897; Tue, 05 Jun 2018 11:51:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528224683; cv=none; d=google.com; s=arc-20160816; b=wj6zVU7jFMq4nV1dTzYm3nI4ZnnXyEyq87mO2B+yyTIZhuPnXMHeV6kH6KfmFsJ7eS yqDd12LHx8W0+eXPKD0mf0MCuBuuIFlJb2j1EuYgEujyiSOJphJ6QGn2P8ZmjcMlRVKL IHb+HIkYpMqkDGiZs4BFdkzq6382GqGtmn6P/t1EFvvmFj96wYN2/xByyGI3JW7DTLQW bLKf3GKancyfz6PxDlzmPVyx7wd/8QNcOyaoHisFZkBa6ZDh4I70t/pQ0seauuMzAAT5 Xmg9xUr4ZbIL3cWY5RHUMzuTv1owwVa1x2mAC2RTSFKsZvdEujv2Hgi5AuZ1gmo8y7wy oPSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:date:message-id :from:references:cc:to:subject:arc-authentication-results; bh=KGttYd74hIVZYOk+C2pIoNRFb8wSkRCm5k8V4Bx/L5c=; b=YwOUMqidHqrwkaGcz9ZlYuMd8HVcRA4tGa9/nLXUjqneu9EreR2k1hmAxqMxYhlxJq WayfsLS8OM1VPjQEzf4F0VWDPTVpaChdnJSQZgrLl85jE9s5jsCHZds5RNHbkyJBkL31 3O2kFmeCBve7dQRnHWRtJn1HJ4gobufF7k0TBeJSpFQ9CjVLh1oBMVR+0lw+JrOsT151 hrqfY3JTco3Mr3gsZsOhl+TS2pl/u5D6D+5TwFOk7Wv2eDWbJrSnNpjH/00wfTeDY3pv TRXGlniATH+06QmgTxQva0dkw0dOUP+Xso67cbf5pVL8oGvlR6YS8clbdw88I3f9Qq/M 9uNA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h66-v6si24186985pgc.53.2018.06.05.11.51.08; Tue, 05 Jun 2018 11:51:23 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752000AbeFESuq (ORCPT + 99 others); Tue, 5 Jun 2018 14:50:46 -0400 Received: from mx1.yrkesakademin.fi ([85.134.45.194]:40109 "EHLO mx1.yrkesakademin.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751812AbeFESup (ORCPT ); Tue, 5 Jun 2018 14:50:45 -0400 Subject: Re: building in 32bit chroot on x86_64 host broken To: Linus Torvalds CC: Masahiro Yamada , Linux Kernel Mailing List References: <8f46ed9a-85c0-8df4-2d1e-d268cbc9d0e9@mageia.org> <7a5458da-4222-7480-00ed-a51bed2c1e39@mageia.org> From: Thomas Backlund Message-ID: Date: Tue, 5 Jun 2018 21:50:56 +0259 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-WatchGuard-Spam-ID: str=0001.0A0C0202.5B16DB85.0103,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-WatchGuard-Spam-Score: 0, clean; 0, virus threat unknown X-WatchGuard-Mail-Client-IP: 85.134.45.194 X-WatchGuard-Mail-From: tmb@mageia.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Den 2018-06-05 kl. 21:38, skrev Linus Torvalds: > On Tue, Jun 5, 2018 at 11:23 AM Thomas Backlund wrote: >> # >> -# CONFIG_64BIT is not set >> >> So something _does_ strip away the needed config bit > Why do you need it? > > I get > > CONFIG_X86_32=y > CONFIG_X86=y > > and CONFIG_64BIT never gets set. > > It is true that I don't get the > > # CONFIG_64BIT is not set > > line, but why do you care? > > Linus Because without it running the build in the 32bit chroot will get the initial reported issue: $ 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) which breaks our buildbots running in chroots... Now I can work around it by adding the config bit myself, but I'd like to understand what changed and why... -- Thomas