From: Michael Ellerman <mpe@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org, Anton Blanchard <anton@samba.org>,
Alan Modra <amodra@gmail.com>
Subject: Re: [PATCH] powerpc/boot: request no dynamic linker for boot wrapper
Date: Mon, 28 Nov 2016 22:07:39 +1100 [thread overview]
Message-ID: <87shqbrhfo.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20161128014226.7656-1-npiggin@gmail.com>
Nicholas Piggin <npiggin@gmail.com> writes:
> 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.
2.28 is not released yet though is it?
So can we just declare versions with that behaviour broken?
> diff --git a/arch/powerpc/boot/wrapper b/arch/powerpc/boot/wrapper
> index 404b3aa..cd941a8 100755
> --- a/arch/powerpc/boot/wrapper
> +++ b/arch/powerpc/boot/wrapper
> @@ -181,6 +181,13 @@ case "$elfformat" in
> elf32-powerpc) format=elf32ppc ;;
> esac
>
> +# Do not include PT_INTERP segment when linking pie. Non-pie linking
> +# just ignores this option.
> +LD_VERSION=$(${CROSS}ld --version | $srctree/scripts/ld-version.sh)
> +LD_NO_DL_MIN_VERSION=$(echo 2.26 | $srctree/scripts/ld-version.sh)
> +if [ "$LD_VERSION" -ge "$LD_NO_DL_MIN_VERSION" ] ; then
> + nodl="--no-dynamic-linker"
> +fi
Some distros (RHEL at least?), ship the wrapper as a standalone script.
So I don't think we can call things in $srctree. Or at least I don't
know how that's supposed to work when it's shipped standalone.
We're also basically reinventing ld-option, which is a PITA.
cheers
next prev parent reply other threads:[~2016-11-28 11:07 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 [this message]
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=87shqbrhfo.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=amodra@gmail.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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 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).