mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Helge Deller <helge.deller@steuerkanzlei-deller.de>
Cc: Guenter Roeck <linux@roeck-us.net>,
	linux-kernel@vger.kernel.org,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Helge Deller <deller@gmx.de>,
	linux-parisc@vger.kernel.org,
	kbuild test robot <fengguang.wu@intel.com>
Subject: Re: parisc:generic-64bit_defconfig build failures due to 'kbuild: handle   libs-y archives separately...'
Date: Wed, 19 Jul 2017 12:01:06 +1000	[thread overview]
Message-ID: <20170719120106.54d6ad1f@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <2eee9t3p9qmqow3xr998vi1a.1500415087874@email.android.com>

On Tue, 18 Jul 2017 23:58:07 +0200
Helge Deller <helge.deller@steuerkanzlei-deller.de> wrote:

>     
> This outstanding patch will fix it:
> https://patchwork.kernel.org/patch/9832033/
> Helge 
> Von meinem Samsung Gerät gesendet.

Thanks for the quick fix. I'm not sure why 0day didn't catch it.
Does it build test parisc/generic-64bit_defconfig, I wonder?

Thanks,
Nick


> 
> -------- Ursprüngliche Nachricht --------
> Von: Guenter Roeck <linux@roeck-us.net> 
> Datum: 18.07.17  17:21  (GMT+01:00) 
> An: Nicholas Piggin <npiggin@gmail.com> 
> Cc: linux-kernel@vger.kernel.org, Masahiro Yamada <yamada.masahiro@socionext.com>, "James E.J. Bottomley" <jejb@parisc-linux.org>, Helge Deller <deller@gmx.de>, linux-parisc@vger.kernel.org 
> Betreff: parisc:generic-64bit_defconfig build failures due to 'kbuild: handle
  libs-y archives separately...' 
> 
> Hi,
> 
> parisc64 builds, specifically generic-64bit_defconfig, fail to build
> in mainline as follows.
> 
> hppa64-linux-ld:
> hppa64-linux/bin/../lib/gcc/hppa64-linux/4.9.0/libgcc.a(_divdi3.o)(.text+0xec):
> cannot reach $$divU
> hppa64-linux/bin/../lib/gcc/hppa64-linux/4.9.0/libgcc.a(_divdi3.o):
> In function `__divdi3':
> libgcc2.c:(.text+0xec): relocation truncated to fit: R_PARISC_PCREL22F against
> symbol `$$divU' defined in .text.div section in
> hppa64-linux/bin/../lib/gcc/hppa64-linux/4.9.0/libgcc.a(_divU.o)
> hppa64-linux-ld:
> hppa64-linux/bin/../lib/gcc/hppa64-linux/4.9.0/libgcc.a(_divdi3.o)(.text+0x150):
> cannot reach $$divU
> 
> [ and many more ]
> 
> This is after enabling CONFIG_MLONGCALLS; otherwise build failures are
> more severe.
> 
> Building with gcc 6.3.0 fails as well with the same error.
> 
> Bisect points to commit 3a166fc2d4ef ("kbuild: handle libs-y archives
> separately from built-in.o archives") as the culprit. Bisect log is
> attached.

       reply	other threads:[~2017-07-19  2:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2eee9t3p9qmqow3xr998vi1a.1500415087874@email.android.com>
2017-07-19  2:01 ` Nicholas Piggin [this message]
2017-07-19  2:10   ` Fengguang Wu
2017-07-19  2:45     ` Li, Philip
2017-07-18 15:21 Guenter Roeck
2017-07-18 23:11 ` John David Anglin

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=20170719120106.54d6ad1f@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=deller@gmx.de \
    --cc=fengguang.wu@intel.com \
    --cc=helge.deller@steuerkanzlei-deller.de \
    --cc=jejb@parisc-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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

all inboxes | Powered by JetHome®