From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Remi Machet" <rmachet@slac.stanford.edu>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 4/5] powerpc: Make the 64-bit kernel as a position-independent executable
Date: Thu, 9 Oct 2008 01:07:32 -0600 [thread overview]
Message-ID: <fa686aa40810090007u27908fd6p1234acff06c75761@mail.gmail.com> (raw)
In-Reply-To: <1222474260.19465.24.camel@pcds-ts102.slac.stanford.edu>
On Fri, Sep 26, 2008 at 6:10 PM, Remi Machet <rmachet@slac.stanford.edu> wrote:
> Hi Paul,
>
> This patch breaks my build with the following error:
>
> /u1/rmachet/projects/c2k/linux-powerpc-git $ make cuImage.c2k modules ARCH=powerpc V=1
> ...
> powerpc-linux-gnu-ld -m elf32ppc -Bstatic -o .tmp_vmlinux1 -T arch/powerpc/kernel/vmlinux.lds arch/powerpc/kernel/head_32.o arch/powerpc/kernel/fpu.o init/built-in.o --start-group usr/built-in.o arch/powerpc/kernel/built-in.o arch/powerpc/mm/built-in.o arch/powerpc/lib/built-in.o arch/powerpc/sysdev/built-in.o arch/powerpc/platforms/built-in.o kernel/built-in.o mm/built-in.o fs/built-in.o ipc/built-in.o security/built-in.o crypto/built-in.o block/built-in.o lib/lib.a lib/built-in.o drivers/built-in.o sound/built-in.o firmware/built-in.o net/built-in.o --end-group
> powerpc-linux-gnu-ld: BFD 2.16.1 internal error, aborting at /u1/rmachet/project/crosstool/crosstool-0.43/build/powerpc-linux-gnu/gcc-4.1.1-glibc-2.3.6/binutils-2.16.1/bfd/elflink.c line 6419 in elf_link_output_extsym
>
> powerpc-linux-gnu-ld: Please report this bug.
I can confirm this problem. This patch breaks builds using binutils
2.16.1. It definitely looks like a binutils bug. It builds fine with
2.17.
>
> I isolated the problem to line 202 in arch/powerpc/kernel/vmlinux.lds.S: If I remove that
> line then the kernel builds and run fine on my board (a PowerPC 32bits c2k).
> For reference the line is:
>
> .rela.dyn : AT(ADDR(.rela.dyn) - LOAD_OFFSET)
> {
> 202-> __rela_dyn_start = .;
> *(.rela*)
> }
There are still a lot of embedded developers using 2.16.1 binutils in
their toolchains so I think that this needs to be worked around.
Otherwise we'll see lots of complaints when this gets merged into
mainline. However, I haven't figured out a workaround yet. Looking
at the binutils sourcecode doesn't reveal anything obvious, but it's
too late for my brain to work properly. Anyone else have any ideas?
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-10-09 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 1:43 [PATCH 4/5] powerpc: Make the 64-bit kernel as a position-independent executable Paul Mackerras
2008-09-27 0:10 ` Remi Machet
2008-10-09 7:07 ` Grant Likely [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-13 1:27 [PATCH 0/5] Relocatable 64-bit kernel using linker PIE support Paul Mackerras
2008-08-13 1:36 ` [PATCH 4/5] powerpc: Make the 64-bit kernel as a position-independent executable Paul Mackerras
2008-08-19 16:20 ` Geert Uytterhoeven
2008-08-20 6:34 ` Paul Mackerras
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=fa686aa40810090007u27908fd6p1234acff06c75761@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=rmachet@slac.stanford.edu \
/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).