Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751796AbXKJJWS (ORCPT ); Sat, 10 Nov 2007 04:22:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750857AbXKJJWH (ORCPT ); Sat, 10 Nov 2007 04:22:07 -0500 Received: from emailhub.stusta.mhn.de ([141.84.69.5]:42696 "EHLO mailhub.stusta.mhn.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750805AbXKJJWF (ORCPT ); Sat, 10 Nov 2007 04:22:05 -0500 Date: Sat, 10 Nov 2007 10:21:41 +0100 From: Adrian Bunk To: Paul Mundt , Sam Ravnborg , Jeff Garzik , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , LKML , Linus Torvalds , Andrew Morton Subject: Re: [PATCH 0/11 v3] enable "make ARCH=x86" Message-ID: <20071110092140.GJ26163@stusta.de> References: <20071109230812.GA5176@uranus.ravnborg.org> <4735242B.1010801@garzik.org> <20071110075444.GA5707@uranus.ravnborg.org> <20071110082152.GA18632@linux-sh.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20071110082152.GA18632@linux-sh.org> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1994 Lines: 48 On Sat, Nov 10, 2007 at 05:21:52PM +0900, Paul Mundt wrote: > On Sat, Nov 10, 2007 at 08:54:44AM +0100, Sam Ravnborg wrote: > > 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. > > When it was decided to unify i386 and x86_64 it was at the same time > > decided to handle them as a *single* architecture. > > > > Keeping ARCH=i386 and ARCH=x86_64 around is just a way to pretend > > this is two diffrent architectures which is no longer the case. > > If you do that, then things like randconfigs will randomly break if you > happen to use a toolchain targetted specifically at i386 or so. >... If you want to know how to restrict randconfig to CONFIG_X86_32 with an unified architecture you should either read the toplevel README in the kernel sources or an older email of mine in this thread... 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/