From: Bob Tracy <rct@gherkin.frus.com>
To: linux-alpha@vger.kernel.org
Cc: debian-alpha@lists.debian.org, mcree@orcon.net.nz,
mattst88@gmail.com, rth@twiddle.net
Subject: [BUG] 4.9.0 build error on Alpha
Date: Thu, 29 Dec 2016 21:08:46 -0600 [thread overview]
Message-ID: <20161230030846.GA25929@gherkin.frus.com> (raw)
I'm guessing this is Alpha-specific at the moment, because I'm getting a
world-class lettin' alone from the kernel developers.
Saw another binutils update come through a couple of days ago, so tried
another from-scratch kernel build. No change in the outcome. This
"smells" like a gcc or binutils issue, because the Alpha-specific code
being compiled and linked against hasn't changed in a very long time.
Both "strcat" and "stxcpy" come from assembly language source files in
the "arch/alpha/lib" directory.
In addition to trying new toolchain components as updates appear, I've
tried making various changes to my kernel configuration in an attempt to
make the problem move to a different place in the build process or go
away entirely. Nothing has had any effect whatsoever.
I would reluctantly try downgrading gcc to version 4.x if someone
thought that might make any difference. I'd rather identify how the
current toolchain is going off in the weeds, if that's what is going on
here.
> LD init/built-in.o
> arch/alpha/lib/lib.a(strcat.o): In function `strcat':
> (.text+0x60): relocation truncated to fit: BRADDR against symbol `__stxcpy' defined in .text section in arch/alpha/lib/lib.a(stxcpy.o)
> arch/alpha/lib/lib.a(strncat.o): In function `strncat':
> (.text+0x60): relocation truncated to fit: BRADDR against symbol `__stxncpy' defined in .text section in arch/alpha/lib/lib.a(stxncpy.o)
> Makefile:969: recipe for target 'vmlinux' failed
> make: *** [vmlinux] Error 1
--Bob
next reply other threads:[~2016-12-30 3:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 3:08 Bob Tracy [this message]
2016-12-30 3:23 ` [BUG] 4.9.0 build error on Alpha Matt Turner
2016-12-30 3:37 ` Bob Tracy
2016-12-30 16:02 ` Maciej W. Rozycki
2016-12-30 21:07 ` Helge Deller
2016-12-31 6:43 ` Bob Tracy
2016-12-31 7:20 ` Bob Tracy
2016-12-31 10:11 ` Maciej W. Rozycki
2016-12-31 15:20 ` Bob Tracy
2016-12-31 19:38 ` Michael Cree
2016-12-31 21:09 ` Bob Tracy
2017-01-01 1:23 ` Maciej W. Rozycki
2017-01-01 3:32 ` Bob Tracy
2017-01-01 20:29 ` Bob Tracy
2017-01-03 0:15 ` Bob Tracy
2017-01-12 12:52 ` Maciej W. Rozycki
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=20161230030846.GA25929@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=linux-alpha@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=rth@twiddle.net \
/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