From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-in-05.arcor-online.net (mail-in-05.arcor-online.net [151.189.21.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.arcor.de", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id 28CF7DDF1C for ; Tue, 29 May 2007 16:27:03 +1000 (EST) In-Reply-To: <20070529053445.GD30266@localhost.localdomain> References: <20070529032924.GA30266@localhost.localdomain> <20070529053445.GD30266@localhost.localdomain> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <5dbbc18a80b465a00d6bbb764c06af86@kernel.crashing.org> From: Segher Boessenkool Subject: Re: Don't use HOSTCFLAGS in BOOTCFLAGS Date: Tue, 29 May 2007 08:26:49 +0200 To: David Gibson Cc: linuxppc-dev@ozlabs.org, Paul Mackerras List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >> Also, is there any reason why you can't simply use $(CC) -m32 with >> the kernel $(CFLAGS) ? > > I did think about that. But the kernel CFLAGS does includes > -ffixed-r2 and -Iarch/powerpc which I don't think we want here. Both of these should be fairly harmless. But sure, it is cleaner to have separate flags -- the booter and the kernel run in different environments, after all. Segher