From: Michael Ellerman <mpe@ellerman.id.au>
To: Alan Modra <amodra@gmail.com>
Cc: linuxppc-dev@ozlabs.org, joel@jms.id.au
Subject: Re: [PATCH 1/2] powerpc/vmlinux.lds: Explicitly retain .gnu.hash
Date: Fri, 27 Mar 2020 20:29:02 +1100 [thread overview]
Message-ID: <87369uw3hd.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20200227062147.GC32593@bubble.grove.modra.org>
Alan Modra <amodra@gmail.com> writes:
> On Thu, Feb 27, 2020 at 03:59:32PM +1100, Michael Ellerman wrote:
>> Relocatable kernel builds produce a warning about .gnu.hash being an
>> orphan section:
>>
>> ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in section `.gnu.hash'
>>
>> If we try to discard it the build fails:
>>
>> ld -EL -m elf64lppc -pie --orphan-handling=warn --build-id -o
>> .tmp_vmlinux1 -T ./arch/powerpc/kernel/vmlinux.lds --whole-archive
>> arch/powerpc/kernel/head_64.o arch/powerpc/kernel/entry_64.o
>> ...
>> sound/built-in.a net/built-in.a virt/built-in.a --no-whole-archive
>> --start-group lib/lib.a --end-group
>> ld: could not find section .gnu.hash
>>
>> So add an entry to explicitly retain it, as we do for .hash.
>
> Looks fine to me. You can also pass --hash-style=sysv to ld (since
> binutils-2.18) to disable generation of .gnu.hash.
Our current minimum is 2.21, so that's probably 5-10 years away :)
cheers
next prev parent reply other threads:[~2020-03-27 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 4:59 [PATCH 1/2] powerpc/vmlinux.lds: Explicitly retain .gnu.hash Michael Ellerman
2020-02-27 4:59 ` [PATCH 2/2] powerpc/vmlinux.lds: Discard .interp section Michael Ellerman
2020-02-27 6:27 ` Alan Modra
2020-03-27 9:27 ` Michael Ellerman
2020-02-27 6:21 ` [PATCH 1/2] powerpc/vmlinux.lds: Explicitly retain .gnu.hash Alan Modra
2020-03-27 9:29 ` Michael Ellerman [this message]
2020-04-01 12:53 ` 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=87369uw3hd.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=amodra@gmail.com \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@ozlabs.org \
/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).