All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Brian Norris <briannorris@chromium.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kbuild@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v2] tools build: Provide consistent build options for fixdep
Date: Thu, 15 Aug 2024 13:06:55 +0200	[thread overview]
Message-ID: <Zr3hTzZqsISEqSeh@krava> (raw)
In-Reply-To: <20240815072046.1002837-1-agordeev@linux.ibm.com>

On Thu, Aug 15, 2024 at 09:20:46AM +0200, Alexander Gordeev wrote:
> The fixdep binary is being compiled and linked in one step. While
> the host linker flags are passed to the compiler the host compiler
> flags are missed.
> 
> That leads to build errors at least on x86_64, arm64 and s390 as
> result of the compiler vs linker flags inconsistency. For example,
> during RPM package build redhat-hardened-ld script is provided to
> gcc, while redhat-hardened-cc1 script is missed.
> 
> Provide both KBUILD_HOSTCFLAGS and KBUILD_HOSTLDFLAGS to avoid that.
> 
> Closes: https://lore.kernel.org/lkml/99ae0d34-ed76-4ca0-a9fd-c337da33c9f9@leemhuis.info/
> Fixes: ea974028a049 ("tools build: Avoid circular .fixdep-in.o.cmd issues")
> Tested-by: Thorsten Leemhuis <linux@leemhuis.info>
> Reviewed-by: Brian Norris <briannorris@chromium.org>
> Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>

Acked-by: Jiri Olsa <jolsa@kernel.org>

jirka

> ---
> 
> This patch is against kernel-next next-20240815 tag
> 
> v2:
> - missing tags added
> - commit message adjusted
> 
> ---
>  tools/build/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/build/Makefile b/tools/build/Makefile
> index fea3cf647f5b..18ad131f6ea7 100644
> --- a/tools/build/Makefile
> +++ b/tools/build/Makefile
> @@ -44,4 +44,4 @@ ifneq ($(wildcard $(TMP_O)),)
>  endif
>  
>  $(OUTPUT)fixdep: $(srctree)/tools/build/fixdep.c
> -	$(QUIET_CC)$(HOSTCC) $(KBUILD_HOSTLDFLAGS) -o $@ $<
> +	$(QUIET_CC)$(HOSTCC) $(KBUILD_HOSTCFLAGS) $(KBUILD_HOSTLDFLAGS) -o $@ $<
> -- 
> 2.43.0
> 
> 

      reply	other threads:[~2024-08-15 11:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15  7:20 [PATCH v2] tools build: Provide consistent build options for fixdep Alexander Gordeev
2024-08-15 11:06 ` Jiri Olsa [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=Zr3hTzZqsISEqSeh@krava \
    --to=olsajiri@gmail.com \
    --cc=acme@redhat.com \
    --cc=agordeev@linux.ibm.com \
    --cc=bpf@vger.kernel.org \
    --cc=briannorris@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.