[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071110035025.GI26163@stusta.de>
Date: Sat, 10 Nov 2007 04:50:25 +0100
From: Adrian Bunk <bunk@...nel.org>
To: Jeff Garzik <jeff@...zik.org>
Cc: Sam Ravnborg <sam@...nborg.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/11 v3] enable "make ARCH=x86"
On Fri, Nov 09, 2007 at 10:23:23PM -0500, Jeff Garzik wrote:
> Sam Ravnborg wrote:
>> This is the patch that get rid of ARCH=i386 and ARCH=x86_64
>> and introduce ARCH=x86.
>> It touches several files but the changes are all one or two-liners.
>>
>> x86: drop backward compatibility symlinks to i386/boot and x86_64/boot
>> kbuild: sanity check the specified arch
>
>
> IMO it negatives impacts the workflow when you -remove- the ability to set
> 32/64-bit on the make command line.
>
> Building and testing for both architectures now requires the additional
> step of editing .config, which is a clear workflow negative impact at least
> for me.
>
> I switch between other cross-compiled arches (alpha, usually) on the
> makefile command line
>
> Yes, I know other 32/64-bit arches require .config editing. That doesn't
> change the basic fact that this is a workflow regression.
With KCONFIG_ALLCONFIG you can avoid the editing of the .config and set
32/64-bit on the make command line - and it's not limited to the
32/64-bit choice:
$ cat /home/jeff/myi386config
CONFIG_HIGHMEM64G=y
CONFIG_X86_32=y
CONFIG_SMP=n
CONFIG_PCI=n
CONFIG_IPV6=m
$ make allyesconfig KCONFIG_ALLCONFIG=/home/jeff/myi386config
> Jeff
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
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