[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTik2ggnZYixbVPVDgQjUIsJVW-UQyItmR-soghc0@mail.gmail.com>
Date: Thu, 27 May 2010 18:19:35 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Randy Dunlap <rdunlap@...otime.net>
Cc: Américo Wang <xiyou.wangcong@...il.com>,
Jaswinder Singh Rajput <jaswinderlinux@...il.com>,
"Rafael J. Wysocki" <rjw@...k.pl>, Sam Ravnborg <sam@...nborg.org>,
Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: config automatically switches from 32-bit to 64-bit for x86
On Thu, May 27, 2010 at 07:31, Randy Dunlap <rdunlap@...otime.net> wrote:
> On Thu, 27 May 2010 12:31:23 +0800 Américo Wang wrote:
>> On Thu, May 27, 2010 at 09:39:51AM +0530, Jaswinder Singh Rajput wrote:
>> >On Thu, May 27, 2010 at 5:43 AM, Rafael J. Wysocki <rjw@...k.pl> wrote:
>> >> On Thursday 27 May 2010, Jaswinder Singh Rajput wrote:
>> >>> Hello,
>> >>>
>> >>> I am trying to build 32 bit kernel image on 64-bit machine but after
>> >>> 'make menuconfig' it automatically switches 32-bit to 64-bit.
>> >>
>> >> Try 'linux32 make menuconfig' and 'linux32 make'.
>> >>
>> >
>> >Yes, this works :-)
>>
>>
>> I think 'make ARCH=i386 menuconfig' also works.
>
> Yes, that's what I use. I wasn't familiar with the "linux32 make ..." usage.
Doesn't the linux32 trick run the (possibly slower due to x86 register pressure)
32-bit compiler instead of running the 64-bit compiler in -m32 mode?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists