From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] kirk: install only if sources are present
Date: Mon, 10 Nov 2025 09:40:28 +0100 [thread overview]
Message-ID: <20251110084028.GA1244228@pevik> (raw)
In-Reply-To: <20251110-kirk_makefile_install_fix-v1-1-e3f01e0cd53e@suse.com>
Hi Andrea,
> Fix kirk Makefile, so source code is copied during install process
> only if it's present.
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
> tools/kirk/Makefile | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
> diff --git a/tools/kirk/Makefile b/tools/kirk/Makefile
> index 1a09c43ce..876eb3e2e 100644
> --- a/tools/kirk/Makefile
> +++ b/tools/kirk/Makefile
> @@ -10,13 +10,15 @@ include $(top_srcdir)/include/mk/env_pre.mk
> BASE_DIR := $(abspath $(DESTDIR)/$(prefix))
> install:
> +ifneq ($(wildcard $(abs_srcdir)/kirk-src/libkirk/*.py),)
Maybe add:
Fixes: 4db20e7d79 ("kirk: move kirk source code inside tools/kirk/kirk-src")
LGTM.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
FYI tools/sparse/Makefile runs 'git submodule update --init' if source code
does not exists:
$(SPARSE_SRC)/Makefile:
ifeq ($(SPARSE_SRC),sparse-src)
git submodule update --init
else
$(error "Can't find $(SPARSE_SRC)/Makefile")
endif
Because it filters out tools/sparse in tools/Makefile, this gets applied only
when sparse is really needed (i.e. via 'make check' or cd into the directory).
> 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
Although I acked the change to move Makefile to LTP, thinking about it twice I'm
not convinced that it's a much better solution than keeping Makefile outside. I
understand you don't want to keep LTP specific Makefile in kirk, but having to
keep kirk paths in LTP is not optimal either (during experimenting with a
different version one will have to update the Makefile).
Kind regards,
Petr
> + 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 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 8:10 [LTP] [PATCH] kirk: install only if sources are present Andrea Cervesato
2025-11-10 8:40 ` 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=20251110084028.GA1244228@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.