From: Michael Ellerman <mpe@ellerman.id.au>
To: Joel Stanley <joel@jms.id.au>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Michal Marek <michal.lkml@markovi.net>,
Daniel Axtens <dja@axtens.net>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 2/2] powerpc/boot: Set target when cross-compiling for clang
Date: Mon, 12 Nov 2018 22:14:07 +1100 [thread overview]
Message-ID: <87muqea6ps.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20181112042116.5271-3-joel@jms.id.au>
Joel Stanley <joel@jms.id.au> writes:
> Clang needs to be told which target it is building for when cross
> compiling.
>
> Link: https://github.com/ClangBuiltLinux/linux/issues/259
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> ---
> arch/powerpc/boot/Makefile | 5 +++++
> 1 file changed, 5 insertions(+)
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
cheers
> diff --git a/arch/powerpc/boot/Makefile b/arch/powerpc/boot/Makefile
> index 39354365f54a..111f97b1ccec 100644
> --- a/arch/powerpc/boot/Makefile
> +++ b/arch/powerpc/boot/Makefile
> @@ -55,6 +55,11 @@ BOOTAFLAGS := -D__ASSEMBLY__ $(BOOTCFLAGS) -traditional -nostdinc
>
> BOOTARFLAGS := -cr$(KBUILD_ARFLAGS)
>
> +ifdef CONFIG_CC_IS_CLANG
> +BOOTCFLAGS += $(CLANG_FLAGS)
> +BOOTAFLAGS += $(CLANG_FLAGS)
> +endif
> +
> ifdef CONFIG_DEBUG_INFO
> BOOTCFLAGS += -g
> endif
> --
> 2.19.1
next prev parent reply other threads:[~2018-11-12 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 4:21 [PATCH v2 0/2] powerpc/boot: Fix cross compiling with clang Joel Stanley
2018-11-12 4:21 ` [PATCH v2 1/2] Makefile: Export clang toolchain variables Joel Stanley
2018-11-12 18:55 ` Nick Desaulniers
2018-11-13 5:16 ` Masahiro Yamada
2018-11-13 23:34 ` Masahiro Yamada
2018-11-12 4:21 ` [PATCH v2 2/2] powerpc/boot: Set target when cross-compiling for clang Joel Stanley
2018-11-12 11:14 ` Michael Ellerman [this message]
2018-11-12 19:03 ` Nick Desaulniers
2018-11-13 23:25 ` Masahiro Yamada
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=87muqea6ps.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=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=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