From: Nicolas Schier <nsc@kernel.org>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@cloudflare.com,
"Nathan Chancellor" <nathan@kernel.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
stable@vger.kernel.org
Subject: Re: [PATCH v1] kbuild: Fix CC_CAN_LINK detection
Date: Fri, 13 Feb 2026 17:29:26 +0100 [thread overview]
Message-ID: <aY9RZkRY0CqkZBdQ@derry.ads.avm.de> (raw)
In-Reply-To: <20260212133544.1331437-1-mic@digikod.net>
On Thu, Feb 12, 2026 at 02:35:43PM +0100, Mickaël Salaün wrote:
> Most samples cannot be build on some environments because they depend
> on CC_CAN_LINK, which is set according to the result of
> scripts/cc-can-link.sh called by cc_can_link_user.
>
> Because cc-can-link.sh must now build without warning, it may fail
> because it is calling printf() with an empty string:
>
> + cat
> + gcc -m32 -Werror -Wl,--fatal-warnings -x c - -o /dev/null
> <stdin>: In function ‘main’:
> <stdin>:4:9: error: zero-length gnu_printf format string [-Werror=format-zero-length]
> cc1: all warnings being treated as errors
>
> Fix this warning and the samples build by actually printing something.
>
> Cc: Nathan Chancellor <nathan@kernel.org>
> Cc: Nicolas Schier <nsc@kernel.org>
> Cc: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> Cc: stable@vger.kernel.org
> Fixes: d81d9d389b9b ("kbuild: don't enable CC_CAN_LINK if the dummy program generates warnings")
> Signed-off-by: Mickaël Salaün <mic@digikod.net>
> ---
> scripts/cc-can-link.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Thanks!
Reviewed-by: Nicolas Schier <nsc@kernel.org>
next prev parent reply other threads:[~2026-02-13 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 13:35 [PATCH v1] kbuild: Fix CC_CAN_LINK detection Mickaël Salaün
2026-02-12 14:15 ` Thomas Weißschuh
2026-02-12 14:50 ` Mickaël Salaün
2026-02-13 16:29 ` Nicolas Schier [this message]
2026-02-18 20:49 ` Nathan Chancellor
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=aY9RZkRY0CqkZBdQ@derry.ads.avm.de \
--to=nsc@kernel.org \
--cc=kernel-team@cloudflare.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--cc=nathan@kernel.org \
--cc=stable@vger.kernel.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