From: Nathan Chancellor <nathan@kernel.org>
To: Askar Safin <safinaskar@gmail.com>
Cc: linux-kbuild@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
regressions@lists.linux.dev, linux-kernel@vger.kernel.org,
miguel.ojeda.sandonis@gmail.com, nsc@kernel.org,
ojeda@kernel.org, sam@gentoo.org,
thomas.weissschuh@linutronix.de, Daniel Xu <dxu@dxuuu.xyz>
Subject: Re: [REGRESSION][BISECTED] kbuild: CFLAGS=-w no longer works
Date: Thu, 9 Oct 2025 10:41:20 -0700 [thread overview]
Message-ID: <20251009174120.GA442207@ax162> (raw)
In-Reply-To: <20251009075149.1083040-1-safinaskar@gmail.com>
Hi Askar,
On Thu, Oct 09, 2025 at 10:51:49AM +0300, Askar Safin wrote:
> #regzbot introduced: d1d0963121769d8d16150b913fe886e48efefa51
>
> As well as I understand, if you want to disable warnings, you
> should pass "CFLAGS=-w" to "make". Starting with d1d096312176,
> this no longer works.
>
> Steps to reproduce:
>
> $ cd linux
> $ git clean -f -q -d -x # To clean everything not controlled by git
> $ echo 'CONFIG_64BIT=y' > /tmp/minimini
> $ make allnoconfig KCONFIG_ALLCONFIG=/tmp/minimini
> $ make -j32 CFLAGS=-w
As Nicolas pointed out, CFLAGS has not be hooked into Kbuild for a long
time, see commit 69ee0b352242 ("kbuild: do not pick up CFLAGS from the
environment"). You would need to use KCFLAGS=-w to accomplish the same
thing. KCFLAGS is only for the kernel build though, you would need
HOSTCFLAGS=-w as well to ignore warnings when building the host
programs such as objtool.
It does seem like the objtool Makefile should be hardened against CFLAGS
being passed in from the command line so that the build does not break
like this though.
Cheers,
Nathan
next prev parent reply other threads:[~2025-10-09 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 7:51 [REGRESSION][BISECTED] kbuild: CFLAGS=-w no longer works Askar Safin
2025-10-09 8:02 ` Askar Safin
2025-10-09 8:48 ` Nicolas Schier
2025-10-15 2:55 ` Askar Safin
2025-10-09 17:41 ` Nathan Chancellor [this message]
2025-12-03 20:05 ` Askar Safin
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=20251009174120.GA442207@ax162 \
--to=nathan@kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=safinaskar@gmail.com \
--cc=sam@gentoo.org \
--cc=thomas.weissschuh@linutronix.de \
/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