Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752815AbdFVGUP (ORCPT ); Thu, 22 Jun 2017 02:20:15 -0400 Received: from ozlabs.org ([103.22.144.67]:39029 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751163AbdFVGUN (ORCPT ); Thu, 22 Jun 2017 02:20:13 -0400 Date: Thu, 22 Jun 2017 16:20:11 +1000 From: Stephen Rothwell To: Nicholas Piggin Cc: David Miller , Linux-Next Mailing List , Linux Kernel Mailing List , Masahiro Yamada Subject: Re: linux-next: build failure after merge of most trees Message-ID: <20170622162011.583d68d0@canb.auug.org.au> In-Reply-To: <20170622154952.0c66951b@roar.ozlabs.ibm.com> References: <20170622152441.3704b3d9@canb.auug.org.au> <20170622154952.0c66951b@roar.ozlabs.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 858 Lines: 26 Hi Nicholas, On Thu, 22 Jun 2017 15:49:52 +1000 Nicholas Piggin wrote: > > It could be this > > https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git/commit/?h=thin-ar&id=ec2c9c20f0efab37ae31de44fe0617aa61283905 > > kbuild: handle libs-y archives separately from built-in.o archives > > That touches the lib linking code regardless of CONFIG_THIN_ARCHIVE. > You should be able to revert it by itself (which will break a few > other archs, so you would also have to revert the default y patch > for thin archives to repair your tree if this is the cause). Yeah, reverting that commit fixes the sparc64 build. (i have not done that in today;s linux-next release, however). > I'll try to get around to it after I fix up some other arch breakage > caused by the series :) Thanks. -- Cheers, Stephen Rothwell