Re: linux-next: build failure after merge of most trees

From: Date: Fri, 23 Jun 2017 06:46:53 + > I will insert this before Nicholas' series. Thank you.

Re: linux-next: build failure after merge of most trees

From: Date: Fri, 23 Jun 2017 06:46:53 + > I will insert this before Nicholas' series. Thank you.

Re: linux-next: build failure after merge of most trees

> > > Cc: npig...@gmail.com; linux-n...@vger.kernel.org; > > linux-kernel@vger.kernel.org; Yamada, Masahiro/山田 真弘 > > <yamada.masah...@socionext.com>; amo...@gmail.com > > Subject: Re: linux-next: build failure after merge of most trees > > > > Hi all, &g

Re: linux-next: build failure after merge of most trees

t; linux-kernel@vger.kernel.org; Yamada, Masahiro/山田 真弘 > > ; amo...@gmail.com > > Subject: Re: linux-next: build failure after merge of most trees > > > > Hi all, > > > > On Thu, 22 Jun 2017 10:56:48 -0400 (EDT) David Miller > > wrote: > > >

RE: linux-next: build failure after merge of most trees

; Yamada, Masahiro/山田 真弘 > <yamada.masah...@socionext.com>; amo...@gmail.com > Subject: Re: linux-next: build failure after merge of most trees > > Hi all, > > On Thu, 22 Jun 2017 10:56:48 -0400 (EDT) David Miller <da...@davemloft.net> > wrote: > > > > Feel free to

RE: linux-next: build failure after merge of most trees

.@gmail.com > Subject: Re: linux-next: build failure after merge of most trees > > Hi all, > > On Thu, 22 Jun 2017 10:56:48 -0400 (EDT) David Miller > wrote: > > > > Feel free to merge it into your series: > > > > [snip] > > I a

Re: linux-next: build failure after merge of most trees

Hi all, On Thu, 22 Jun 2017 10:56:48 -0400 (EDT) David Miller wrote: > > Feel free to merge it into your series: > > > sparc64: Use indirect calls in hamming weight stubs. > > Otherwise, depending upon link order, the branch relocation > limits could

Re: linux-next: build failure after merge of most trees

Hi all, On Thu, 22 Jun 2017 10:56:48 -0400 (EDT) David Miller wrote: > > Feel free to merge it into your series: > > > sparc64: Use indirect calls in hamming weight stubs. > > Otherwise, depending upon link order, the branch relocation > limits could be exceeded. > >

Re: linux-next: build failure after merge of most trees

On Thu, 22 Jun 2017 10:29:23 -0400 (EDT) David Miller wrote: > From: David Miller > Date: Thu, 22 Jun 2017 10:13:06 -0400 (EDT) > > > From: Nicholas Piggin > > Date: Thu, 22 Jun 2017 18:41:16 +1000 > > > >> Is there any way for

Re: linux-next: build failure after merge of most trees

On Thu, 22 Jun 2017 10:29:23 -0400 (EDT) David Miller wrote: > From: David Miller > Date: Thu, 22 Jun 2017 10:13:06 -0400 (EDT) > > > From: Nicholas Piggin > > Date: Thu, 22 Jun 2017 18:41:16 +1000 > > > >> Is there any way for the linker to place the inputs to avoid unresolvable > >>

Re: linux-next: build failure after merge of most trees

On Thu, 22 Jun 2017 10:56:48 -0400 (EDT) David Miller wrote: > From: Nicholas Piggin > Date: Fri, 23 Jun 2017 00:33:39 +1000 > > > On Thu, 22 Jun 2017 10:13:06 -0400 (EDT) > > David Miller wrote: > > > >> From: Nicholas Piggin

Re: linux-next: build failure after merge of most trees

On Thu, 22 Jun 2017 10:56:48 -0400 (EDT) David Miller wrote: > From: Nicholas Piggin > Date: Fri, 23 Jun 2017 00:33:39 +1000 > > > On Thu, 22 Jun 2017 10:13:06 -0400 (EDT) > > David Miller wrote: > > > >> From: Nicholas Piggin > >> Date: Thu, 22 Jun 2017 18:41:16 +1000 > >> > >> > Is

Re: linux-next: build failure after merge of most trees

From: Nicholas Piggin Date: Fri, 23 Jun 2017 00:33:39 +1000 > On Thu, 22 Jun 2017 10:13:06 -0400 (EDT) > David Miller wrote: > >> From: Nicholas Piggin >> Date: Thu, 22 Jun 2017 18:41:16 +1000 >> >> > Is there any way for the linker

Re: linux-next: build failure after merge of most trees

From: Nicholas Piggin Date: Fri, 23 Jun 2017 00:33:39 +1000 > On Thu, 22 Jun 2017 10:13:06 -0400 (EDT) > David Miller wrote: > >> From: Nicholas Piggin >> Date: Thu, 22 Jun 2017 18:41:16 +1000 >> >> > Is there any way for the linker to place the inputs to avoid unresolvable >> > relocations

Re: linux-next: build failure after merge of most trees

On Thu, 22 Jun 2017 23:43:10 +0930 Alan Modra wrote: > On Thu, Jun 22, 2017 at 06:41:16PM +1000, Nicholas Piggin wrote: > > Is there any way for the linker to place the inputs to avoid unresolvable > > relocations where possible? > > Not without quite a lot of work writing

Re: linux-next: build failure after merge of most trees

On Thu, 22 Jun 2017 23:43:10 +0930 Alan Modra wrote: > On Thu, Jun 22, 2017 at 06:41:16PM +1000, Nicholas Piggin wrote: > > Is there any way for the linker to place the inputs to avoid unresolvable > > relocations where possible? > > Not without quite a lot of work writing support for that

Re: linux-next: build failure after merge of most trees

On Thu, 22 Jun 2017 10:13:06 -0400 (EDT) David Miller wrote: > From: Nicholas Piggin > Date: Thu, 22 Jun 2017 18:41:16 +1000 > > > Is there any way for the linker to place the inputs to avoid unresolvable > > relocations where possible? > > I don't

Re: linux-next: build failure after merge of most trees

On Thu, 22 Jun 2017 10:13:06 -0400 (EDT) David Miller wrote: > From: Nicholas Piggin > Date: Thu, 22 Jun 2017 18:41:16 +1000 > > > Is there any way for the linker to place the inputs to avoid unresolvable > > relocations where possible? > > I don't think so. > > > A way to work around this

Re: linux-next: build failure after merge of most trees

From: David Miller Date: Thu, 22 Jun 2017 10:13:06 -0400 (EDT) > From: Nicholas Piggin > Date: Thu, 22 Jun 2017 18:41:16 +1000 > >> Is there any way for the linker to place the inputs to avoid unresolvable >> relocations where possible? > > I don't

Re: linux-next: build failure after merge of most trees

From: David Miller Date: Thu, 22 Jun 2017 10:13:06 -0400 (EDT) > From: Nicholas Piggin > Date: Thu, 22 Jun 2017 18:41:16 +1000 > >> Is there any way for the linker to place the inputs to avoid unresolvable >> relocations where possible? > > I don't think so. > >> A way to work around this is

Re: linux-next: build failure after merge of most trees

On Thu, Jun 22, 2017 at 06:41:16PM +1000, Nicholas Piggin wrote: > Is there any way for the linker to place the inputs to avoid unresolvable > relocations where possible? Not without quite a lot of work writing support for that feature. -- Alan Modra Australia Development Lab, IBM

Re: linux-next: build failure after merge of most trees

On Thu, Jun 22, 2017 at 06:41:16PM +1000, Nicholas Piggin wrote: > Is there any way for the linker to place the inputs to avoid unresolvable > relocations where possible? Not without quite a lot of work writing support for that feature. -- Alan Modra Australia Development Lab, IBM

Re: linux-next: build failure after merge of most trees

From: Nicholas Piggin Date: Thu, 22 Jun 2017 18:41:16 +1000 > Is there any way for the linker to place the inputs to avoid unresolvable > relocations where possible? I don't think so. > A way to work around this is to make arch/sparc/lib/hweight.o an obj-y > rather than

Re: linux-next: build failure after merge of most trees

From: Nicholas Piggin Date: Thu, 22 Jun 2017 18:41:16 +1000 > Is there any way for the linker to place the inputs to avoid unresolvable > relocations where possible? I don't think so. > A way to work around this is to make arch/sparc/lib/hweight.o an obj-y > rather than lib-y. That's a hack

Re: linux-next: build failure after merge of most trees

CC'ing Alan 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):

Re: linux-next: build failure after merge of most trees

CC'ing Alan 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:

Re: linux-next: build failure after merge of most trees

Hi Nick, On Thu, 22 Jun 2017 16:20:11 +1000 Stephen Rothwell wrote: > > On Thu, 22 Jun 2017 15:49:52 +1000 Nicholas Piggin wrote: > > > > It could be this > > > >

Re: linux-next: build failure after merge of most trees

Hi Nick, On Thu, 22 Jun 2017 16:20:11 +1000 Stephen Rothwell wrote: > > On Thu, 22 Jun 2017 15:49:52 +1000 Nicholas Piggin wrote: > > > > It could be this > > > >

Re: linux-next: build failure after merge of most trees

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=ec2c9c20f0efab37ae31de44fe0617aa61283905 > > kbuild: handle libs-y archives

Re: linux-next: build failure after merge of most trees

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=ec2c9c20f0efab37ae31de44fe0617aa61283905 > > kbuild: handle libs-y archives separately from

Re: linux-next: build failure after merge of most trees

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

Re: linux-next: build failure after merge of most trees

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:

linux-next: build failure after merge of most trees

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

linux-next: build failure after merge of most trees

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