From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sunset.davemloft.net (unknown [74.93.104.97]) by ozlabs.org (Postfix) with ESMTP id 34A35DDE2F for ; Thu, 8 Feb 2007 23:00:05 +1100 (EST) Date: Thu, 08 Feb 2007 04:00:03 -0800 (PST) Message-Id: <20070208.040003.112623191.davem@davemloft.net> To: paulus@samba.org Subject: Re: Kbuild change breaks the ppc64 build From: David Miller In-Reply-To: <17867.1342.763881.188430@cargo.ozlabs.ibm.com> References: <17867.1342.763881.188430@cargo.ozlabs.ibm.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Cc: linuxppc-dev@ozlabs.org, olecom@flower.upol.cz, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Paul Mackerras Date: Thu, 8 Feb 2007 22:10:54 +1100 > Commit 5de043f4bd11a9e0a3e8daec7d1905da575a76b7 breaks the build on > 64-bit powerpc because we no longer get the -m64 flag passed to gcc. > There is code in arch/powerpc/Makefile which adds (or used to add) > -m64 to AS, LD and CC if we are running on a 64-bit machine (which I > am) and have a biarch toolchain (which I do). Without -m64, the > toolchain assumes 32-bit and all sorts of things break spectacularly. > > I haven't yet tracked down exactly why this commit has this effect, > since I find it takes considerable time and effort to understand > Kbuild. It's this commit: commit 5de043f4bd11a9e0a3e8daec7d1905da575a76b7 Author: Oleg Verych Date: Tue Feb 6 02:18:21 2007 +0100 [PATCH] kbuild: improve option checking, Kbuild.include cleanup GNU binutils, root users, tmpfiles, external modules ro builds must be fixed to do the right thing now. Cc: Roman Zippel Cc: Sam Ravnborg Cc: Horst Schirmeier Cc: Jan Beulich Cc: Daniel Drake Cc: Andi Kleen Cc: Randy Dunlap Signed-off-by: Oleg Verych Signed-off-by: Linus Torvalds Linus and Oleg tried to fix it with various subsequent changes to scripts/Kbuild.include, but it's still broken. For some reason $(call ...) invocations add spaces. I tried another test case: define test $(shell echo -n) endef VAR:=$(call test) all: @echo "\'$(VAR)\'" And this always prints: ' TEST' even with GNU Make version 3.81 If I put a $(strip ...) around the define, the space is still there. If I put the $(strip ...) around VAR's $(call), the space goes away.