From: Alistair Popple <alistair@popple.id.au>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: Don't use ELFv2 ABI to build the kernel
Date: Tue, 19 Nov 2013 15:06:18 +1100 [thread overview]
Message-ID: <3514005.hxHnfdoU4C@mexican> (raw)
In-Reply-To: <20131119032553.GA27740@concordia>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Tue, 19 Nov 2013 14:25:53 Michael Ellerman wrote:
> On Mon, Nov 18, 2013 at 05:21:34PM +1100, Alistair Popple wrote:
> > The kernel doesn't build correctly using the ELFv2 ABI. This patch
> > ensures that the ELFv1 ABI is used when building a kernel with an
> > ELFv2 enabled compiler.
>
> Let me check I've got this straight.
>
> The ELFv2 ABI is still being developed, so there are no released
> toolchains that support it right?
I believe ELFv2 patches started going upstream to gcc last week.
> So this patch is precautionary, in that it means kernels from this
> commit onward will build correctly with newer toolchains. Anyone wanting
> to build an older kernel with a new toolchain will need to backport this
> patch?
No, only people wanting to build PPC64 little endian kernels with newer
toolchains should need this (as ELFv2 is the default for PPC64LE). In all
cases execpt PPC64LE the newer toolchains should default to ELFv1.
> cheers
Regards,
Alistair
[-- Attachment #2: Type: text/html, Size: 5114 bytes --]
prev parent reply other threads:[~2013-11-19 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 6:21 [PATCH] powerpc: Don't use ELFv2 ABI to build the kernel Alistair Popple
2013-11-18 19:29 ` Scott Wood
2013-11-19 0:46 ` Alistair Popple
2013-11-19 3:25 ` Michael Ellerman
2013-11-19 4:06 ` Alistair Popple [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=3514005.hxHnfdoU4C@mexican \
--to=alistair@popple.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
/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