From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"Sam Ravnborg" <sam@ravnborg.org>, "Ingo Molnar" <mingo@elte.hu>,
"Andrew Morton" <akpm@linux-foundation.org>,
"the arch/x86 maintainers" <x86@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: config automatically switches from 32-bit to 64-bit for x86
Date: Thu, 27 May 2010 17:03:29 +0800 [thread overview]
Message-ID: <20100527090329.GF5349@cr0.nay.redhat.com> (raw)
In-Reply-To: <AANLkTilZ99VsmLuYoLlYItYAMtQQq6zTOQ2iEAdEm7pk@mail.gmail.com>
On Thu, May 27, 2010 at 10:53:41AM +0530, Jaswinder Singh Rajput wrote:
>On Thu, May 27, 2010 at 10:01 AM, Américo Wang <xiyou.wangcong@gmail.com> wrote:
>> On Thu, May 27, 2010 at 09:39:51AM +0530, Jaswinder Singh Rajput wrote:
>>>
>>>But I wonder then what is the point/use of CONFIG_X86_32 if compiler
>>>is not listening to it.
>>>
>>>Logically compiler should set appropriate flags based on .config settings.
>>>
>>
>> It's not compiler, it's kbuild, kbuild tries to determine the arch
>> by 'uname -m'.
>>
>
>Ahh, then kbuild is buggy, kbuild should check .config instead of
>'uname -m' and verify from user if it mismatches.
>
Why? You didn't use 'make oldconfig', why shoud it check?
next prev parent reply other threads:[~2010-05-27 8:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 0:07 config automatically switches from 32-bit to 64-bit for x86 Jaswinder Singh Rajput
2010-05-27 0:13 ` Rafael J. Wysocki
2010-05-27 4:09 ` Jaswinder Singh Rajput
2010-05-27 4:31 ` Américo Wang
2010-05-27 5:23 ` Jaswinder Singh Rajput
2010-05-27 9:03 ` Américo Wang [this message]
2010-05-27 5:31 ` Randy Dunlap
2010-05-27 16:19 ` Geert Uytterhoeven
2010-05-27 20:21 ` Rafael J. Wysocki
2010-05-27 15:19 ` Matthias Schniedermeyer
2010-05-27 15:49 ` Christoph Hellwig
2010-05-27 16:11 ` Matthias Schniedermeyer
2010-05-27 16:13 ` Christoph Hellwig
2010-05-27 16:35 ` Matthias Schniedermeyer
2010-05-27 18:46 ` Sam Ravnborg
2010-05-27 22:07 ` Jaswinder Singh Rajput
2010-05-29 11:19 ` Sam Ravnborg
2010-05-29 17:19 ` Jaswinder Singh Rajput
2010-06-02 8:20 ` Américo Wang
2010-06-02 8:50 ` Sam Ravnborg
2010-06-03 13:30 ` Michal Marek
2010-06-04 6:23 ` Jaswinder Singh Rajput
2010-06-04 7:53 ` Michal Marek
2010-06-06 4:14 ` Jaswinder Singh Rajput
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=20100527090329.GF5349@cr0.nay.redhat.com \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=sam@ravnborg.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.