From: Guenter Roeck <linux@roeck-us.net>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Douglas Anderson <dianders@chromium.org>,
Jonas Karlman <jonas@kwiboo.se>,
Michal Marek <michal.lkml@markovi.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Revert "Makefile: install modules.builtin even if CONFIG_MODULES=n"
Date: Fri, 19 Jun 2020 08:41:54 -0700 [thread overview]
Message-ID: <20200619154154.GA210604@roeck-us.net> (raw)
On Sat, Jun 20, 2020 at 12:09:55AM +0900, Masahiro Yamada wrote:
> This reverts commit e0b250b57dcf403529081e5898a9de717f96b76b,
> which broke build systems that need to install files to a certain
> path, but do not set INSTALL_MOD_PATH when invoking 'make install'.
>
> $ make INSTALL_PATH=/tmp/destdir install
> mkdir: cannot create directory ‘/lib/modules/5.8.0-rc1+/’: Permission denied
> Makefile:1342: recipe for target '_builtin_inst_' failed
> make: *** [_builtin_inst_] Error 1
>
> While modules.builtin is useful also for CONFIG_MODULES=n, this change
> in the behavior is quite unexpected. Maybe "make modules_install"
> can install modules.builtin irrespective of CONFIG_MODULES as Jonas
> originally suggested.
>
> Anyway, that commit should be reverted ASAP.
>
> Reported-by: Douglas Anderson <dianders@chromium.org>
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Cc: Jonas Karlman <jonas@kwiboo.se>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Tested-by: Guenter Roeck <linux@roeck-us.net>
> ---
>
> Changes in v2:
> - add more commit description
>
> Makefile | 14 +++-----------
> 1 file changed, 3 insertions(+), 11 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 29abe44ada91..9880e911afe3 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1336,16 +1336,6 @@ dt_binding_check: scripts_dtc
> # ---------------------------------------------------------------------------
> # Modules
>
> -# install modules.builtin regardless of CONFIG_MODULES
> -PHONY += _builtin_inst_
> -_builtin_inst_:
> - @mkdir -p $(MODLIB)/
> - @cp -f modules.builtin $(MODLIB)/
> - @cp -f $(objtree)/modules.builtin.modinfo $(MODLIB)/
> -
> -PHONY += install
> -install: _builtin_inst_
> -
> ifdef CONFIG_MODULES
>
> # By default, build modules as well
> @@ -1389,7 +1379,7 @@ PHONY += modules_install
> modules_install: _modinst_ _modinst_post
>
> PHONY += _modinst_
> -_modinst_: _builtin_inst_
> +_modinst_:
> @rm -rf $(MODLIB)/kernel
> @rm -f $(MODLIB)/source
> @mkdir -p $(MODLIB)/kernel
> @@ -1399,6 +1389,8 @@ _modinst_: _builtin_inst_
> ln -s $(CURDIR) $(MODLIB)/build ; \
> fi
> @sed 's:^:kernel/:' modules.order > $(MODLIB)/modules.order
> + @cp -f modules.builtin $(MODLIB)/
> + @cp -f $(objtree)/modules.builtin.modinfo $(MODLIB)/
> $(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modinst
>
> # This depmod is only for convenience to give the initial
> --
> 2.25.1
>
next reply other threads:[~2020-06-19 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 15:41 Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-19 15:09 [PATCH v2] Revert "Makefile: install modules.builtin even if CONFIG_MODULES=n" Masahiro Yamada
2020-06-19 15:40 ` Guenter Roeck
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=20200619154154.GA210604@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dianders@chromium.org \
--cc=hch@lst.de \
--cc=jonas@kwiboo.se \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@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