From: "Brian Cain" <bcain@codeaurora.org>
To: "'Masahiro Yamada'" <masahiroy@kernel.org>,
<linux-hexagon@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] hexagon: suppress error message for 'make clean'
Date: Fri, 24 Apr 2020 14:06:21 -0500 [thread overview]
Message-ID: <009101d61a6b$71f93a70$55ebaf50$@codeaurora.org> (raw)
In-Reply-To: <20200424161502.656103-1-masahiroy@kernel.org>
> -----Original Message-----
> From: linux-hexagon-owner@vger.kernel.org <linux-hexagon-
> owner@vger.kernel.org> On Behalf Of Masahiro Yamada
...
> 'make ARCH=hexagon clean' emits an error message as follows:
>
> $ make ARCH=hexagon clean
> gcc: error: unrecognized command line option '-G0'
>
> You can suppress it by setting the correct CROSS_COMPILE=, but we should
> not require any compiler for cleaning.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Acked-by: Brian Cain <bcain@codeaurora.org>
> ---
>
> arch/hexagon/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/hexagon/Makefile b/arch/hexagon/Makefile index
> 4c5858b80f0e..c168c6980d05 100644
> --- a/arch/hexagon/Makefile
> +++ b/arch/hexagon/Makefile
> @@ -30,7 +30,7 @@ TIR_NAME := r19
> KBUILD_CFLAGS += -ffixed-$(TIR_NAME) -
> DTHREADINFO_REG=$(TIR_NAME) -D__linux__ KBUILD_AFLAGS += -
> DTHREADINFO_REG=$(TIR_NAME)
>
> -LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name)
> +LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name
> +2>/dev/null)
> libs-y += $(LIBGCC)
>
> head-y := arch/hexagon/kernel/head.o
> --
> 2.25.1
next prev parent reply other threads:[~2020-04-24 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 16:15 [PATCH] hexagon: suppress error message for 'make clean' Masahiro Yamada
2020-04-24 19:06 ` Brian Cain [this message]
2020-05-01 5:33 ` 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='009101d61a6b$71f93a70$55ebaf50$@codeaurora.org' \
--to=bcain@codeaurora.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.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).