public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Miller <davem@davemloft•net>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext•com>,
	Nicholas Piggin <npiggin@gmail•com>
Subject: linux-next: build failure after merge of most trees
Date: Thu, 22 Jun 2017 15:24:41 +1000	[thread overview]
Message-ID: <20170622152441.3704b3d9@canb.auug.org.au> (raw)

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.

I am using powerpc-le hosted cross compilers:
	gcc 5.2.0
	binutsila 2.25.2

I have left it broken for now.

32 bit sparc is not affected.

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2017-06-22  5:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22  5:24 Stephen Rothwell [this message]
2017-06-22  5:49 ` linux-next: build failure after merge of most trees Nicholas Piggin
2017-06-22  6:20   ` Stephen Rothwell
2017-06-22  6:23     ` Stephen Rothwell
2017-06-22  8:41 ` Nicholas Piggin
2017-06-22 14:13   ` David Miller
2017-06-22 14:29     ` David Miller
2017-06-23  3:40       ` Nicholas Piggin
2017-06-22 14:33     ` Nicholas Piggin
2017-06-22 14:56       ` David Miller
2017-06-23  3:34         ` Nicholas Piggin
2017-06-23  6:43         ` Stephen Rothwell
2017-06-23  6:46           ` yamada.masahiro
2017-06-23  7:04             ` Stephen Rothwell
2017-06-23 15:13             ` David Miller
2017-06-22 14:13   ` Alan Modra
2017-06-22 14:43     ` Nicholas Piggin

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=20170622152441.3704b3d9@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=npiggin@gmail$(echo .)com \
    --cc=yamada.masahiro@socionext$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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