From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] kirk: install only if sources are present
Date: Mon, 10 Nov 2025 10:16:46 +0100 [thread overview]
Message-ID: <20251110091646.GA1246253@pevik> (raw)
In-Reply-To: <20251110-kirk_makefile_install_fix-v2-1-d1f61d4fa23a@suse.com>
Hi Andrea,
> Fix kirk Makefile, so source code is copied during install process
> only if it's present.
> Fixes: 4db20e7d79 ("kirk: move kirk source code inside tools/kirk/kirk-src")
+1, thank you.
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
> Changes in v2:
> - git submodule --init if we are inside the folder or during make check
> - Link to v1: https://lore.kernel.org/r/20251110-kirk_makefile_install_fix-v1-1-e3f01e0cd53e@suse.com
> ---
> tools/kirk/Makefile | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
> diff --git a/tools/kirk/Makefile b/tools/kirk/Makefile
> index 1a09c43ce..10c45789c 100644
> --- a/tools/kirk/Makefile
> +++ b/tools/kirk/Makefile
> @@ -8,15 +8,25 @@ top_srcdir ?= ../..
> include $(top_srcdir)/include/mk/env_pre.mk
> BASE_DIR := $(abspath $(DESTDIR)/$(prefix))
> +KIRK_SRC ?= kirk-src
Is it really useful to have directory optional? (I'm not sure this is useful for
sparse).
> +
> +$(KIRK_SRC)/Makefile:
> +ifeq ($(KIRK_SRC),sparse-src)
> + git submodule update --init
This will always run "git submodule update --init" even on top level make
install. This requires "make install" to have internet connection. Therefore I
would prefer to skip kirk on top level "make install".
-FILTER_OUT_DIRS += sparse
+FILTER_OUT_DIRS += kirk sparse
And what is the difference? I see slightly better having:
'cd tools/kirk && make && make install' than
'git submodule init tools/ltx/ltx-src' or
'git submodule update --init'.
If you don't agree, I'm not against the first version.
Kind regards,
Petr
> +else
> + $(error "Can't find $(KIRK_SRC)/Makefile")
> +endif
> install:
> +ifneq ($(wildcard $(abs_srcdir)/kirk-src/libkirk/*.py),)
> mkdir -p $(BASE_DIR)/libkirk
> mkdir -p $(BASE_DIR)/libkirk/channels
> - install -m 00644 $(top_srcdir)/tools/kirk/kirk-src/libkirk/*.py $(BASE_DIR)/libkirk
> - install -m 00644 $(top_srcdir)/tools/kirk/kirk-src/libkirk/channels/*.py $(BASE_DIR)/libkirk/channels
> - install -m 00775 $(top_srcdir)/tools/kirk/kirk-src/kirk $(BASE_DIR)/kirk
> + install -m 00644 $(abs_srcdir)/kirk-src/libkirk/*.py $(BASE_DIR)/libkirk
> + install -m 00644 $(abs_srcdir)/kirk-src/libkirk/channels/*.py $(BASE_DIR)/libkirk/channels
> + install -m 00775 $(abs_srcdir)/kirk-src/kirk $(BASE_DIR)/kirk
> cd $(BASE_DIR) && ln -sf kirk runltp-ng
> +endif
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2025-11-10 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 8:53 [LTP] [PATCH v2] kirk: install only if sources are present Andrea Cervesato
2025-11-10 9:16 ` Petr Vorel [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=20251110091646.GA1246253@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.de \
--cc=ltp@lists.linux.it \
/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