From: Daniel Axtens <dja@axtens.net>
To: Joel Stanley <joel@jms.id.au>,
Michael Ellerman <mpe@ellerman.id.au>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] Makefile: Export clang toolchain variables
Date: Mon, 05 Nov 2018 11:10:49 +1100 [thread overview]
Message-ID: <87ftwg4c52.fsf@linkitivity.dja.id.au> (raw)
In-Reply-To: <20181104231133.30848-2-joel@jms.id.au>
Hi Joel,
Thanks!
Tested-by: Daniel Axtens <dja@axtens.net> # powerpc 64-bit BE
Regards,
Daniel
> The powerpc makefile will use these in it's boot wrapper.
>
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> ---
> Makefile | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index 9aa352b38815..a2db3c885b38 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -495,6 +495,9 @@ endif
> ifneq ($(GCC_TOOLCHAIN),)
> CLANG_GCC_TC := --gcc-toolchain=$(GCC_TOOLCHAIN)
> endif
> +export CLANG_TARGET
> +export CLANG_GCC_TC
> +export CLANG_PREFIX
> KBUILD_CFLAGS += $(CLANG_TARGET) $(CLANG_GCC_TC) $(CLANG_PREFIX)
> KBUILD_AFLAGS += $(CLANG_TARGET) $(CLANG_GCC_TC) $(CLANG_PREFIX)
> KBUILD_CFLAGS += $(call cc-option, -no-integrated-as)
> --
> 2.19.1
next prev parent reply other threads:[~2018-11-05 0:11 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 [this message]
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 ` [PATCH 0/2] poewrpc/Boot: Fix cross compiling with clang Nick Desaulniers
2018-11-06 0:36 ` 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=87ftwg4c52.fsf@linkitivity.dja.id.au \
--to=dja@axtens.net \
--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=ndesaulniers@google.com \
--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).