From: "Chris Friesen" <cfriesen@nortel.com>
To: linuxppc-dev@ozlabs.org, Linux kernel <linux-kernel@vger.kernel.org>
Subject: build failure on powerpc with current -git
Date: Fri, 17 Oct 2008 13:32:59 -0600 [thread overview]
Message-ID: <48F8E86B.702@nortel.com> (raw)
The current -git fails to build on 64-bit powerpc (failure log below) .
Initially I tried using my older toolchain, when I first saw the
problem I built a new toolchain with crosstool (gcc 4.1.2 and binutils
2.16.1) and tried again but got the same problem.
2.6.27 doesn't show this problem.
Any ideas what's going on and how I can fix it?
Thanks,
Chris
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 4 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
/opt/crosstool/gcc-4.1.2-glibc-2.3.6/powerpc64-unknown-linux-gnu/bin/powerpc64-unknown-linux-gnu-ld:
BFD 2.16.1 internal error, aborting at
/home/cfriesen/crosstool-0.43/build/powerpc64-unknown-linux-gnu/gcc-4.1.2-glibc-2.3.6/binutils-2.16.1/bfd/elflink.c
line 6419 in elf_link_output_extsym
/opt/crosstool/gcc-4.1.2-glibc-2.3.6/powerpc64-unknown-linux-gnu/bin/powerpc64-unknown-linux-gnu-ld:
Please report this bug.
make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [sub-make] Error 2
next reply other threads:[~2008-10-17 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 19:32 Chris Friesen [this message]
2008-10-18 6:49 ` build failure on powerpc with current -git Grant Likely
2008-10-21 5:33 ` Paul Mackerras
2008-10-21 8:13 ` Stephen Rothwell
2008-10-22 3:58 ` Paul Mackerras
2008-10-22 15:21 ` Hollis Blanchard
2008-10-22 17:49 ` Chris Friesen
[not found] ` <fb412d760810220819o1a15d47ej198f6e15c3e63f15@mail.gmail.com>
2008-10-22 17:50 ` Chris Friesen
2008-10-23 0:19 ` Josh Boyer
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=48F8E86B.702@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/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