From: Nick Desaulniers <ndesaulniers@google.com>
To: joel@jms.id.au
Cc: mpe@ellerman.id.au,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/2] poewrpc/Boot: Fix cross compiling with clang
Date: Mon, 5 Nov 2018 14:37:44 -0800 [thread overview]
Message-ID: <CAKwvOdm8WZTeB_wxkO2nN7PW=v=2z7tdVapTq-TiB18nZZfS=A@mail.gmail.com> (raw)
In-Reply-To: <20181104231133.30848-1-joel@jms.id.au>
On Sun, Nov 4, 2018 at 3:11 PM Joel Stanley <joel@jms.id.au> wrote:
>
> Hello,
>
> These patches allow clang to cross-compile the powerpc boot wrapper.
> The boot wrapper constructs it's own compiler flags as it may not be
> built for the same arch as the kernel.
Hi Joel, thanks for the series! I'm just curious, how does the boot
wrapper run on a different arch than the kernel?
>
> The powerpc64le kernel builds natively with clang and with this patch it
> can cross compile too.
>
> Joel Stanley (2):
> Makefile: Export clang toolchain variables
> powerpc/boot: Set target when cross-compiling for clang
>
> Makefile | 3 +++
> arch/powerpc/boot/Makefile | 7 +++++++
> 2 files changed, 10 insertions(+)
>
> --
> 2.19.1
>
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2018-11-05 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 23:11 [PATCH 0/2] poewrpc/Boot: Fix cross compiling with clang Joel Stanley
2018-11-04 23:11 ` [PATCH 1/2] Makefile: Export clang toolchain variables Joel Stanley
2018-11-05 0:10 ` Daniel Axtens
2018-11-05 2:52 ` Masahiro Yamada
2018-11-04 23:11 ` [PATCH 2/2] powerpc/boot: Set target when cross-compiling for clang Joel Stanley
2018-11-05 0:11 ` Daniel Axtens
2018-11-05 22:37 ` Nick Desaulniers [this message]
2018-11-06 0:36 ` [PATCH 0/2] poewrpc/Boot: Fix cross compiling with clang Joel Stanley
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='CAKwvOdm8WZTeB_wxkO2nN7PW=v=2z7tdVapTq-TiB18nZZfS=A@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=joel@jms.id.au \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michal.lkml@markovi.net \
--cc=mpe@ellerman.id.au \
--cc=yamada.masahiro@socionext.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).