From: Alan Modra <amodra@gmail.com>
To: Nicholas Piggin <npiggin@gmail.com>, Nick Clifton <nickc@redhat.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH] powerpc/boot: request no dynamic linker for boot wrapper
Date: Mon, 28 Nov 2016 12:56:04 +1030 [thread overview]
Message-ID: <20161128022604.GE26291@bubble.grove.modra.org> (raw)
In-Reply-To: <20161128014226.7656-1-npiggin@gmail.com>
On Mon, Nov 28, 2016 at 12:42:26PM +1100, Nicholas Piggin wrote:
> The boot wrapper performs its own relocations and does not require
> PT_INTERP segment.
OK, so the kernel change is quite reasonable in isolation, but see
below.
> 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:
So this change added space for another header, it seems. I suspect
that was accidental, particularly since there was no mention of
get_program_header_size in the ChangeLog entry.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2016-11-28 2:26 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 [this message]
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
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=20161128022604.GE26291@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nickc@redhat.com \
--cc=npiggin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.