From: Sam Ravnborg <sam@ravnborg.org>
To: Nathan Lynch <ntl@pobox.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: "do section mismatch check on full vmlinux" breaks powerpc build
Date: Wed, 25 Jul 2007 11:50:59 +0200 [thread overview]
Message-ID: <20070725095059.GA25580@uranus.ravnborg.org> (raw)
In-Reply-To: <20070724224105.GG951@localdomain>
On Tue, Jul 24, 2007 at 05:41:05PM -0500, Nathan Lynch wrote:
> Hello-
>
> 2.6.23-rc1 breaks the build for 64-bit powerpc for me (using
> maple_defconfig):
>
> LD vmlinux.o
> powerpc64-unknown-linux-gnu-ld: dynreloc miscount for
> kernel/built-in.o, section .opd
> powerpc64-unknown-linux-gnu-ld: can not edit opd Bad value
> make: *** [vmlinux.o] Error 1
>
> This is on a i386 host with:
> powerpc64-unknown-linux-gnu-gcc (GCC) 4.1.2
> GNU ld version 2.16.1
>
> Reverting the following commit fixes it:
>
> commit 741f98fe298a73c9d47ed53703c1279a29718581
> Author: Sam Ravnborg <sam@ravnborg.org>
> Date: Tue Jul 17 10:54:06 2007 +0200
>
> kbuild: do section mismatch check on full vmlinux
>
>
> However, I see a possibly related binutils patch:
> http://article.gmane.org/gmane.comp.gnu.binutils/33650
>
> Will there be a kbuild fix for this or should I update my binutils?
Did a bit more testing.
Im am down to the following to reproduce the fault:
/opt/crosstool/gcc-4.1.0-glibc-2.3.6/powerpc64-unknown-linux-gnu/bin/powerpc64-unknown-linux-gnu-ld -m elf64ppc -r -o vmlinux.o kernel/signal.o arch/powerpc/kernel/vdso.o
Seems that vdso.o and signal.o does not like each other??
Sam
next prev parent reply other threads:[~2007-07-25 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 22:41 "do section mismatch check on full vmlinux" breaks powerpc build Nathan Lynch
2007-07-25 7:57 ` Sam Ravnborg
2007-07-25 9:50 ` Sam Ravnborg [this message]
2007-07-25 11:43 ` Sam Ravnborg
2007-07-25 21:16 ` Nathan Lynch
2007-07-25 21:33 ` Sam Ravnborg
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=20070725095059.GA25580@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.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;
as well as URLs for NNTP newsgroup(s).