From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Cc: Daniel Wagner <wagi@monom.org>
Subject: [PATCH] trace-cmd documentation: Remove check-manpages.sh for trace-cmd in meson build
Date: Thu, 25 Jul 2024 11:26:20 -0400 [thread overview]
Message-ID: <20240725112620.17c6d1b2@gandalf.local.home> (raw)
From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
The creation of man pages for trace-cmd ran the check-manpages.sh script,
which is only used for the libtracecmd library, not the tools. This caused
the build to spit out warning of grep not finding libtracecmd.txt.
Fixes: 736df0648d16b ("trace-cmd: Add initial support for meson")
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
Documentation/trace-cmd/meson.build | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/Documentation/trace-cmd/meson.build b/Documentation/trace-cmd/meson.build
index d0cc3076d985..875d72832a0b 100644
--- a/Documentation/trace-cmd/meson.build
+++ b/Documentation/trace-cmd/meson.build
@@ -104,13 +104,6 @@ if get_option('docbook-suppress-sp')
xmlto_extra += ['-m ', confdir + 'manpage-suppress-sp.xsl']
endif
-check_doc = custom_target(
- 'check-doc',
- output: 'dummy',
- command : [
- top_source_dir + 'check-manpages.sh',
- meson.current_source_dir()])
-
gen = generator(
asciidoc,
output: '@BASENAME@.xml',
@@ -131,7 +124,6 @@ foreach txt, section : sources
txt.underscorify() + '_man',
input: xml,
output: '@BASENAME@.' + section,
- depends: check_doc,
command: [
xmlto,
'-m', manpage_xsl,
@@ -145,7 +137,6 @@ foreach txt, section : sources
txt.underscorify() + '_html',
input: txt,
output: '@BASENAME@.html',
- depends: check_doc,
command: [
asciidoc,
'-b', asciidoc_html,
--
2.43.0
next reply other threads:[~2024-07-25 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 15:26 Steven Rostedt [this message]
2024-07-30 16:40 ` [PATCH] trace-cmd documentation: Remove check-manpages.sh for trace-cmd in meson build Daniel Wagner
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=20240725112620.17c6d1b2@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=wagi@monom.org \
/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).