From: Samuel Holland <samuel@sholland.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Christopher Schramm <debian@cschramm.eu>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: readd -w option when vmlinux.o or Module.symver is missing
Date: Wed, 4 Jan 2023 21:34:02 -0600 [thread overview]
Message-ID: <15cd1727-eedd-d476-e52c-2234cf66a5c9@sholland.org> (raw)
In-Reply-To: <20230104140459.1147626-1-masahiroy@kernel.org>
On 1/4/23 08:04, Masahiro Yamada wrote:
> Commit 63ffe00d8c93 ("kbuild: Fix running modpost with musl libc")
> accidentally turned the unresolved symbol warnings into errors when
> vmlinux.o (for in-tree builds) or Module.symver (for external module
> builds) is missing.
>
> In those cases, unresolved symbols are expected, but the -w option
> is not set because 'missing-input' is referenced before set.
>
> Move $(missing-input back to the original place. This should be fine
> for musl libc because vmlinux.o and -w are not added at the same time.
>
> With this change, -w may be passed twice, but it is not a big deal.
>
> Link: https://lore.kernel.org/all/b56a03b8-2a2a-f833-a5d2-cdc50a7ca2bb@cschramm.eu/
> Fixes: 63ffe00d8c93 ("kbuild: Fix running modpost with musl libc")
> Reported-by: Christopher Schramm <debian@cschramm.eu>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> scripts/Makefile.modpost | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
Sorry for the breakage. This works fine for me, with or without vmlinux.o.
Tested-by: Samuel Holland <samuel@sholland.org>
prev parent reply other threads:[~2023-01-05 3:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 14:04 Masahiro Yamada
2023-01-05 3:34 ` Samuel Holland [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=15cd1727-eedd-d476-e52c-2234cf66a5c9@sholland.org \
--to=samuel@sholland.org \
--cc=debian@cschramm.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
/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
all inboxes | Powered by JetHome®