[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190713131642.GU14074@gate.crashing.org>
Date: Sat, 13 Jul 2019 08:16:43 -0500
From: Segher Boessenkool <segher@...nel.crashing.org>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-kernel@...r.kernel.org, Nicholas Piggin <npiggin@...il.com>,
Paul Mackerras <paulus@...ba.org>,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH] powerpc: remove meaningless KBUILD_ARFLAGS addition
On Sat, Jul 13, 2019 at 07:47:44AM -0500, Segher Boessenkool wrote:
> On Sat, Jul 13, 2019 at 12:21:06PM +0900, Masahiro Yamada wrote:
> > The KBUILD_ARFLAGS addition in arch/powerpc/Makefile has never worked
> > in a useful way because it is always overridden by the following code
> > in the top Makefile:
> >
> > # use the deterministic mode of AR if available
> > KBUILD_ARFLAGS := $(call ar-option,D)
> >
> > The code in the top Makefile was added in 2011, by commit 40df759e2b9e
> > ("kbuild: Fix build with binutils <= 2.19").
> >
> > The KBUILD_ARFLAGS addition for ppc has always been dead code from the
> > beginning.
>
> That was added in 43c9127d94d6 to replace my 8995ac870273 from 2007.
>
> Is it no longer supported to build a 64-bit kernel with a toolchain
> that defaults to 32-bit, or the other way around? And with non-native
> toolchains (this one didn't run on Linux, even).
It was an --enable-targets=all toolchain, somewhat common for crosses,
if that matters.
Segher
Powered by blists - more mailing lists