[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <duad4gwchwb6732j6vbh75x6k6cvq5lgxvpm3y3btzy746cmo6@uealeonsqeha>
Date: Tue, 25 Mar 2025 18:12:02 -0700
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the tip-fixes tree
On Wed, Mar 26, 2025 at 10:38:54AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip-fixes tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from builtin-check.c:16:
> In function 'save_argv',
> inlined from 'objtool_run' at builtin-check.c:296:2:
> tools/objtool/include/objtool/warn.h:47:17: error: '%s' directive argument is null [-Werror=format-overflow=]
> 47 | "%s%s%s: objtool: " format "\n", \
> | ^~~~~~~~~~~~~~~~~~~
> tools/objtool/include/objtool/warn.h:92:9: note: in expansion of macro 'WARN'
> 92 | WARN("%s: " format " failed: %s", __func__, ##__VA_ARGS__, strerror(errno))
> | ^~~~
> builtin-check.c:241:25: note: in expansion of macro 'WARN_GLIBC'
> 241 | WARN_GLIBC("strdup(%s)", orig_argv[i]);
> | ^~~~~~~~~~
> cc1: all warnings being treated as errors
>
> Caused (or exposed?) by commit
>
> c5995abe1547 ("objtool: Improve error handling")
>
> I have used the tip-fixes tree from next-20250325 for today.
Thanks, I'll fix this up. With my GCC 14.2.1 I get the same error with
that commit, but for some reason the error goes away with the next
commit.
--
Josh
Powered by blists - more mailing lists