public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Michal Marek <mmarek@suse.cz>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kbuild@vger.kernel.org
Subject: Re: 32bit allyesconfig on 64bit system broke
Date: Wed, 28 Aug 2013 14:05:31 -0700	[thread overview]
Message-ID: <521E661B.1030802@zytor.com> (raw)
In-Reply-To: <520A97C1.6000708@suse.cz>

On 08/13/2013 01:32 PM, Michal Marek wrote:
> Dne 10.8.2013 00:57, Andi Kleen napsal(a):
>>
>> % linux32 make allyesconfig
>> % head .config
>> % head .config
>> #
>> # Automatically generated file; DO NOT EDIT.
>> # Linux/x86 3.11.0-rc4 Kernel Configuration
>> #
>> CONFIG_64BIT=y
>> CONFIG_X86_64=y
>> CONFIG_X86=y
>>
>> This used to work to give me a 32bit allyesconfig.
>> How am I supposed to do this now?
> 
> This changed in ffee0de (x86: Default to ARCH=x86 to avoid overriding
> CONFIG_64BIT). The default $ARCH value on both ix86 and x86_64
> buildhosts is "x86" and CONFIG_64BIT is therefore a user-selectable
> knob. You can do
> 
>   make ARCH=i386 allyesconfig
> 
> to force 32bit. Or the generic way:
> 
>   echo '# CONFIG_64BIT is not set' >base.config
>   KCONFIG_ALLCONFIG=base.config linux32 make allyesconfig
> 

"make ARCH=i386 allyesconfig" has been the standard way to do this for
quite a few years, so that is the forward and backwards compatible way.

	-hpa



  reply	other threads:[~2013-08-28 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 22:57 32bit allyesconfig on 64bit system broke Andi Kleen
2013-08-13 20:32 ` Michal Marek
2013-08-28 21:05   ` H. Peter Anvin [this message]
2013-08-29  6:03     ` Andi Kleen

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=521E661B.1030802@zytor.com \
    --to=hpa@zytor.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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