Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752625AbdFVFuM (ORCPT ); Thu, 22 Jun 2017 01:50:12 -0400 Received: from mail-pg0-f66.google.com ([74.125.83.66]:34022 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751064AbdFVFuK (ORCPT ); Thu, 22 Jun 2017 01:50:10 -0400 Date: Thu, 22 Jun 2017 15:49:52 +1000 From: Nicholas Piggin To: Stephen Rothwell 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: <20170622154952.0c66951b@roar.ozlabs.ibm.com> In-Reply-To: <20170622152441.3704b3d9@canb.auug.org.au> References: <20170622152441.3704b3d9@canb.auug.org.au> Organization: IBM X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) 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: 1743 Lines: 37 On Thu, 22 Jun 2017 15:24:41 +1000 Stephen Rothwell wrote: > Hi Dave, > > After merging almost all the trees, today's linux-next build (sparc64 > defconfig) failed like this: > > arch/sparc/lib/hweight.o: In function `__arch_hweight8': > (.text+0x0): relocation truncated to fit: R_SPARC_WDISP19 against symbol `__sw_hweight8' defined in .text section in lib/hweight.o > arch/sparc/lib/hweight.o: In function `__arch_hweight16': > (.text+0xc): relocation truncated to fit: R_SPARC_WDISP19 against symbol `__sw_hweight16' defined in .text section in lib/hweight.o > arch/sparc/lib/hweight.o: In function `__arch_hweight32': > (.text+0x18): relocation truncated to fit: R_SPARC_WDISP19 against symbol `__sw_hweight32' defined in .text section in lib/hweight.o > arch/sparc/lib/hweight.o: In function `__arch_hweight64': > (.text+0x24): relocation truncated to fit: R_SPARC_WDISP19 against symbol `__sw_hweight64' defined in .text section in lib/hweight.o > > I though it may have been caused by the thin archive changes, but > disabling CONFIG_THIN_ARCHIVE did not fix it. I have cc'd Nick and > Masahiro just in case. 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). I'll try to get around to it after I fix up some other arch breakage caused by the series :) Thanks, Nick