From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: eranian@google.com, Ian Rogers <irogers@google.com>
Subject: [PATCH 2/7] perf doc: Fix doc.dep
Date: Wed, 14 Jul 2021 18:33:38 -0700 [thread overview]
Message-ID: <20210715013343.2286699-3-irogers@google.com> (raw)
In-Reply-To: <20210715013343.2286699-1-irogers@google.com>
The doc.dep dependencies for the Makefile fail to build as
build-docdep.perl is missing. Add this file from git.
Signed-off-by: Ian Rogers <irogers@google.com>
---
tools/perf/Documentation/build-docdep.perl | 46 ++++++++++++++++++++++
1 file changed, 46 insertions(+)
create mode 100755 tools/perf/Documentation/build-docdep.perl
diff --git a/tools/perf/Documentation/build-docdep.perl b/tools/perf/Documentation/build-docdep.perl
new file mode 100755
index 000000000000..ba4205e0302a
--- /dev/null
+++ b/tools/perf/Documentation/build-docdep.perl
@@ -0,0 +1,46 @@
+#!/usr/bin/perl
+
+my %include = ();
+my %included = ();
+
+for my $text (<*.txt>) {
+ open I, '<', $text || die "cannot read: $text";
+ while (<I>) {
+ if (/^include::/) {
+ chomp;
+ s/^include::\s*//;
+ s/\[\]//;
+ $include{$text}{$_} = 1;
+ $included{$_} = 1;
+ }
+ }
+ close I;
+}
+
+# Do we care about chained includes???
+my $changed = 1;
+while ($changed) {
+ $changed = 0;
+ while (my ($text, $included) = each %include) {
+ for my $i (keys %$included) {
+ # $text has include::$i; if $i includes $j
+ # $text indirectly includes $j.
+ if (exists $include{$i}) {
+ for my $j (keys %{$include{$i}}) {
+ if (!exists $include{$text}{$j}) {
+ $include{$text}{$j} = 1;
+ $included{$j} = 1;
+ $changed = 1;
+ }
+ }
+ }
+ }
+ }
+}
+
+while (my ($text, $included) = each %include) {
+ if (! exists $included{$text} &&
+ (my $base = $text) =~ s/\.txt$//) {
+ print "$base.html $base.xml : ", join(" ", keys %$included), "\n";
+ }
+}
--
2.32.0.402.g57bb445576-goog
next prev parent reply other threads:[~2021-07-15 1:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 1:33 [PATCH 0/7] Tidy perf Documentation build Ian Rogers
2021-07-15 1:33 ` [PATCH 1/7] perf doc: Fix perfman.info build Ian Rogers
2021-07-15 1:33 ` Ian Rogers [this message]
2021-07-15 1:33 ` [PATCH 3/7] perf doc: Remove references to user-manual Ian Rogers
2021-07-15 1:33 ` [PATCH 4/7] perf doc: Add info pages to all target Ian Rogers
2021-07-23 18:27 ` Arnaldo Carvalho de Melo
2021-07-23 18:53 ` Arnaldo Carvalho de Melo
2021-07-23 18:56 ` Arnaldo Carvalho de Melo
2021-07-23 21:03 ` Ian Rogers
2021-07-23 22:28 ` Arnaldo
2021-07-15 1:33 ` [PATCH 5/7] perf doc: Remove cmd-list.perl references Ian Rogers
2021-07-15 1:33 ` [PATCH 6/7] perf doc: Remove howto-index.sh related references Ian Rogers
2021-07-15 1:33 ` [PATCH 7/7] perf doc: Reorganize ARTICLES variables Ian Rogers
2021-07-19 19:32 ` [PATCH 0/7] Tidy perf Documentation build Namhyung Kim
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=20210715013343.2286699-3-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).