From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Nicholas Piggin <npiggin@gmail•com>
Cc: linuxppc-dev@lists•ozlabs.org, Anton Blanchard <anton@samba•org>,
Nicholas Piggin <npiggin@gmail•com>,
Alan Modra <amodra@gmail•com>
Subject: Re: powerpc/boot: request no dynamic linker for boot wrapper
Date: Mon, 5 Dec 2016 18:47:04 +1100 (AEDT) [thread overview]
Message-ID: <3tXH085YGKz9tlW@ozlabs.org> (raw)
In-Reply-To: <20161128014226.7656-1-npiggin@gmail.com>
On Mon, 2016-11-28 at 01:42:26 UTC, Nicholas Piggin wrote:
> The boot wrapper performs its own relocations and does not require
> PT_INTERP segment.
>
> Without this option, binutils 2.28 and newer tries to create a program
> header segment due to PT_INTERP, and the link fails because there is no
> space for it.
>
> A recent binutils commit:
> https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=1a9ccd70f9a75dc6b48d340059f28ef3550c107b
> has broken kernel builds:
>
> ld: arch/powerpc/boot/zImage.pseries: Not enough room for program headers, try linking with -N
> ld: final link failed: Bad value
>
> Reported-by: Anton Blanchard <anton@samba•org>
> Signed-off-by: Nicholas Piggin <npiggin@gmail•com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/ff45000fcb56b5b0f1a14a865d3541
cheers
prev parent reply other threads:[~2016-12-05 7:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 1:42 [PATCH] powerpc/boot: request no dynamic linker for boot wrapper Nicholas Piggin
2016-11-28 2:26 ` Alan Modra
2016-11-28 11:07 ` Michael Ellerman
2016-11-28 12:07 ` Nicholas Piggin
2016-11-28 12:39 ` Nick Clifton
2016-11-28 13:02 ` Nicholas Piggin
2016-11-28 14:25 ` Nick Clifton
2016-11-29 1:49 ` Nicholas Piggin
2016-11-29 3:42 ` Michael Ellerman
2016-11-30 17:47 ` Gustavo Luiz Duarte
2016-12-05 7:47 ` Michael Ellerman [this message]
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=3tXH085YGKz9tlW@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=amodra@gmail$(echo .)com \
--cc=anton@samba$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=npiggin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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