From: Segher Boessenkool <segher@kernel.crashing.org>
To: Joel Stanley <joel@jms.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc/vmlinux.lds: Drop binutils < 2.18 workarounds
Date: Thu, 4 Apr 2019 09:53:33 -0500 [thread overview]
Message-ID: <20190404145333.GC8599@gate.crashing.org> (raw)
In-Reply-To: <CACPK8Xes6+j+bjCbqwBLJpvP-Hi_WzbtEwfUSzJjeAW9jwFRKA@mail.gmail.com>
Hi Joel,
On Thu, Apr 04, 2019 at 12:17:40PM +0000, Joel Stanley wrote:
> On Fri, 29 Mar 2019 at 09:53, Segher Boessenkool
> <segher@kernel.crashing.org> wrote:
> > On Fri, Mar 29, 2019 at 05:14:53PM +1030, Joel Stanley wrote:
> > > - NOTES :kernel :notes
> > > + NOTES
> >
> > I think this still need to be
> >
> > NOTES :kernel
> >
> > or the linker will complain. Did you try to build ppc64_defconfig?
>
> Yeah, I did build (and boot, in qemu) the ppc64_defconfig. I tried
> leaving in/removing the :kernel annotation in a bunch of places and as
> long as I had it in the first spot, the kernel linked.
>
> Shall I respin with this added?
Yes please, if only so we are testing the exact same thing :-)
There may be a binutils version difference here.
> > (And I do not know if there are any tools that expect the notes in a phdr,
> > or even specifically the second phdr).
^^^ This question remains?
Segher
next prev parent reply other threads:[~2019-04-04 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 6:44 [PATCH v2] powerpc/vmlinux.lds: Drop binutils < 2.18 workarounds Joel Stanley
2019-03-29 9:53 ` Segher Boessenkool
2019-04-04 12:17 ` Joel Stanley
2019-04-04 14:53 ` Segher Boessenkool [this message]
2019-04-04 14:58 ` Christophe Leroy
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=20190404145333.GC8599@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.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).