From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 29 May 2007 16:33:47 +1000 From: David Gibson To: Segher Boessenkool Subject: Re: Don't use HOSTCFLAGS in BOOTCFLAGS Message-ID: <20070529063347.GA8404@localhost.localdomain> References: <20070529032924.GA30266@localhost.localdomain> <20070529053445.GD30266@localhost.localdomain> <5dbbc18a80b465a00d6bbb764c06af86@kernel.crashing.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <5dbbc18a80b465a00d6bbb764c06af86@kernel.crashing.org> 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: , On Tue, May 29, 2007 at 08:26:49AM +0200, Segher Boessenkool wrote: > >> 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. Well, the -I is potentially dangerous, because it allows people to get away with header file dependecies outside the booter specific headers. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson