linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH v2] kbuild: remove trailing slashes from $(KBUILD_EXTMOD)
Date: Thu, 17 Jun 2021 10:37:09 +0900	[thread overview]
Message-ID: <CAK7LNARLctyjSoVCwLkwrGqRH6QFc93xTP8LFAJVgAz+f4YqFA@mail.gmail.com> (raw)
In-Reply-To: <20210602140213.132936-1-masahiroy@kernel.org>

On Wed, Jun 2, 2021 at 11:02 PM Masahiro Yamada <masahiroy@kernel.org> wrote:
>
> M= (or KBUILD_EXTMOD) generally expects a directory path without any
> trailing slashes, like M=a/b/c.
>
> If you add a trailing slash, like M=a/b/c/, you will get ugly build
> logs (two slashes in a series), but it still works fine as long as it
> is consistent between 'make modules' and 'make modules_install'.
>
> The following commands correctly build and install the modules.
>
>   $ make M=a/b/c/ modules
>   $ sudo make M=a/b/c/ modules_install
>
> Since commit ccae4cfa7bfb ("kbuild: refactor scripts/Makefile.modinst"),
> a problem happens if you add a trailing slash only for modules_install.
>
>   $ make M=a/b/c modules
>   $ sudo make M=a/b/c/ modules_install
>
> No module is installed in this case, Johannes Berg reported. [1]
>
> Trim any trailing slashes from $(KBUILD_EXTMOD).
>
> I used the 'dirname' command to remove all the trailing slashes in
> case someone adds more slashes like M=a/b/c/////. The Make's built-in
> function, $(dir ...) cannot take care of such a case.
>
> [1]: https://lore.kernel.org/lkml/10cc8522b27a051e6a9c3e158a4c4b6414fd04a0.camel@sipsolutions.net/
>
> Fixes: ccae4cfa7bfb ("kbuild: refactor scripts/Makefile.modinst")
> Reported-by: Johannes Berg <johannes@sipsolutions.net>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---

Applied to linux-kbuild.



> Changes in v2:
>   - Use $(filter %/, ) so that the shell invocation is avoided
>     if M= is already good.
>
>  Makefile | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index b79e0e8acbe3..8018b8adbcaf 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -129,6 +129,11 @@ endif
>  $(if $(word 2, $(KBUILD_EXTMOD)), \
>         $(error building multiple external modules is not supported))
>
> +# Remove trailing slashes
> +ifneq ($(filter %/, $(KBUILD_EXTMOD)),)
> +KBUILD_EXTMOD := $(shell dirname $(KBUILD_EXTMOD).)
> +endif
> +
>  export KBUILD_EXTMOD
>
>  # Kbuild will save output files in the current working directory.
> --
> 2.27.0
>


-- 
Best Regards
Masahiro Yamada

      reply	other threads:[~2021-06-17  1:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 14:02 [PATCH v2] kbuild: remove trailing slashes from $(KBUILD_EXTMOD) Masahiro Yamada
2021-06-17  1:37 ` Masahiro Yamada [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=CAK7LNARLctyjSoVCwLkwrGqRH6QFc93xTP8LFAJVgAz+f4YqFA@mail.gmail.com \
    --to=masahiroy@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    /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;
as well as URLs for NNTP newsgroup(s).