Prev: : Fix checkstack warning in bunzip2 library
Next: [PATCH] kernel/power/swap.c: fix typos in comments
From: Christoph Hellwig on 27 May 2010 12:20
On Thu, May 27, 2010 at 06:11:34PM +0200, Matthias Schniedermeyer wrote:
> Just use ARCH=x86. That ARCH respects CONFIG_64BIT from .config and
> "CONFIG_64BIT" is a config-option (the very first in menuconfig)

Which is an obsolute pain to type, even worse than doing a linux32 call
first. Really, a simple

make

should default to do the right thing.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Geert Uytterhoeven on 27 May 2010 12:20
On Thu, May 27, 2010 at 07:31, Randy Dunlap <rdunlap(a)xenotime.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(a)sisk.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(a)linux-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(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Matthias Schniedermeyer on 27 May 2010 12:40
On 27.05.2010 12:13, Christoph Hellwig wrote:
> On Thu, May 27, 2010 at 06:11:34PM +0200, Matthias Schniedermeyer wrote:
> > Just use ARCH=x86. That ARCH respects CONFIG_64BIT from .config and
> > "CONFIG_64BIT" is a config-option (the very first in menuconfig)
>
> Which is an obsolute pain to type, even worse than doing a linux32 call
> first. Really, a simple
>
> make
>
> should default to do the right thing.

In my case it's wonderful, i compile several kernels with different
bitnesses for differnt machines and with ARCH=x86 i don't have to
differentiate between an i386 or x86_64 target.

for dat in a b c d; do make ARCH=x86 O=../$dat ; done





Bis denn

--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Sam Ravnborg on 27 May 2010 14:50
On Thu, May 27, 2010 at 11:49:16AM -0400, Christoph Hellwig wrote:
> On Thu, May 27, 2010 at 05:37:36AM +0530, 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.
> >
> > Is this a BUG or did intentionally.
>
> I think it's intentional, but I'm really annoyed by this behaviour.

The request when we did the merge of 32 and 64 bit was that we
should continue to build 64bit kernels on 64 bit machines.
And likewise for 32bit.
Because this was what the users where used to.

We could simplify metters by defining new rules.
As you suggest that uname on an intel box always resulted in ARCH=x86.
But then people would complain why a 32 bit kernel is default when
the box is 64 bit.

Something like this:
[The escape chars align nicely in the patched Makefile]

Sam

diff --git a/Makefile b/Makefile
index ebc8225..e7f97a5 100644
--- a/Makefile
+++ b/Makefile
@@ -161,10 +161,11 @@ export srctree objtree VPATH
# then ARCH is assigned, getting whatever value it gets normally, and
# SUBARCH is subsequently ignored.

-SUBARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ \
- -e s/arm.*/arm/ -e s/sa110/arm/ \
+SUBARCH := $(shell uname -m | sed -e s/i.86/x86/ -e s/x86_64/x86/ \
+ -e s/sun4u/sparc64/ \
+ -e s/arm.*/arm/ -e s/sa110/arm/ \
-e s/s390x/s390/ -e s/parisc64/parisc/ \
- -e s/ppc.*/powerpc/ -e s/mips.*/mips/ \
+ -e s/ppc.*/powerpc/ -e s/mips.*/mips/ \
-e s/sh[234].*/sh/ )

# Cross compiling and selecting different set of gcc/bin-utils

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Rafael J. Wysocki on 27 May 2010 16:30
On Thursday 27 May 2010, Geert Uytterhoeven wrote:
> On Thu, May 27, 2010 at 07:31, Randy Dunlap <rdunlap(a)xenotime.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(a)sisk.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?

You're probably right, but I haven't noticed a difference yet. :-)

Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: : Fix checkstack warning in bunzip2 library
Next: [PATCH] kernel/power/swap.c: fix typos in comments