linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-kernel@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: remove meaningless KBUILD_ARFLAGS addition
Date: Sat, 13 Jul 2019 07:47:44 -0500	[thread overview]
Message-ID: <20190713124744.GS14074@gate.crashing.org> (raw)
In-Reply-To: <20190713032106.8509-1-yamada.masahiro@socionext.com>

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).


Segher

  reply	other threads:[~2019-07-13 12:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-13  3:21 [PATCH] powerpc: remove meaningless KBUILD_ARFLAGS addition Masahiro Yamada
2019-07-13 12:47 ` Segher Boessenkool [this message]
2019-07-13 13:16   ` Segher Boessenkool
2019-07-13 22:45     ` Masahiro Yamada
2019-07-13 23:54       ` Segher Boessenkool
2019-07-15  7:05         ` Michael Ellerman
2019-07-15  7:29           ` Segher Boessenkool
2019-07-15 12:03             ` Masahiro Yamada
2019-07-15 18:16               ` Segher Boessenkool
2019-07-16  7:14                 ` Masahiro Yamada
2019-07-16 12:15             ` Michael Ellerman
2019-07-17 14:38               ` Segher Boessenkool
2019-07-17 15:19                 ` Masahiro Yamada
2019-07-17 16:46                   ` Segher Boessenkool
2019-07-18  2:19                     ` Masahiro Yamada
2019-07-18 20:46                       ` Segher Boessenkool
2019-07-19  3:39                         ` Michael Ellerman
2019-08-19  4:25                           ` Masahiro Yamada
2019-08-28  4:24 ` Michael Ellerman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190713124744.GS14074@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yamada.masahiro@socionext.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).