From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 1/3] Makefile: Add C header with generated LTP version
Date: Tue, 4 Jul 2023 11:26:30 +0200 [thread overview]
Message-ID: <20230704092630.GB497945@pevik> (raw)
In-Reply-To: <20230704091933.496989-1-pvorel@suse.cz>
Hi,
> Hi,
> obviously this is wrong, because $(top_srcdir)/Version (ltp-version.h
> dependency) is not specified in the top level Makefile (only Version is
> there). But I'm not sure if it should be changed to
> $(top_srcdir)/Version.
> I suppose ltp-version.h should be in include/, but here I'm completely
> lost with dependencies under lib/. My goal is to type make in lib/ and
> make sure the header is generated (dependencies correctly resolved).
> Kind regards,
> Petr
> Petr Vorel (3):
> Makefile: Add C header with generated LTP version
> lib/C-API: Add option -V to print LTP version
> lib/C-API: Print LTP version at test start
> .gitignore | 1 +
> lib/Makefile | 4 ++++
> lib/tst_test.c | 8 ++++++++
> 3 files changed, 13 insertions(+)
please ignore this patch. Subject was supposed to be
"[RFC PATCH 0/3] C API: print LTP version"
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2023-07-04 9:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 9:19 [LTP] [RFC PATCH 1/3] Makefile: Add C header with generated LTP version Petr Vorel
2023-07-04 9:19 ` Petr Vorel
2023-07-04 9:25 ` Petr Vorel
2023-07-13 11:58 ` Cyril Hrubis
2023-07-14 2:54 ` Li Wang
2023-07-14 4:53 ` Petr Vorel
2023-07-14 6:46 ` Cyril Hrubis
2023-07-14 9:25 ` Li Wang
2023-07-04 9:19 ` [LTP] [RFC PATCH 2/3] lib/C-API: Add option -V to print " Petr Vorel
2023-07-04 10:33 ` Cyril Hrubis
2023-07-04 11:50 ` Petr Vorel
2023-07-04 12:04 ` Cyril Hrubis
2023-07-04 12:07 ` Petr Vorel
2023-07-04 9:19 ` [LTP] [RFC PATCH 3/3] lib/C-API: Print LTP version at test start Petr Vorel
2023-07-04 9:26 ` 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=20230704092630.GB497945@pevik \
--to=pvorel@suse.cz \
--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