From: Steven Rostedt <rostedt@goodmis.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: libtracefs documentation install problem
Date: Thu, 24 Dec 2020 12:23:16 -0500 [thread overview]
Message-ID: <20201224122316.357b4538@oasis.local.home> (raw)
In-Reply-To: <CADVatmNE_Bm6Gv9ArNsTQhJME9y7gbnExFf+iy_=68CSKKZ+Xw@mail.gmail.com>
On Thu, 24 Dec 2020 16:36:56 +0000
Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:
> Hi Steve,
>
> I was trying to build and install the documentation. "make doc"
> succeeds and builds the man pages and the html files, but when I do
> "make install_doc" it fails with:
> make -C /home/sudip/libtracefs/Documentation install
> Makefile:148: *** "You need to install asciidoc xmlto for man pages". Stop.
> make: *** [Makefile:263: install_doc] Error 2
Ug, I thought I tested this :-/
>
> The packages asciidoc and xmlto are already installed and I guess
> thats why it could build. Looking at the Documantion makefile I can
> see that install-man is checking for the tools by calling
> 'get-executable' but I did not see 'get-executable' defined anywhere.
> Did I miss something or did you miss copying it from
> "tools/scripts/utilities.mak" of the kernel ?
Probably.
Could you file a bugzilla report so I can get to it on Jan 6 when I go
back to work.
https://bugzilla.kernel.org/buglist.cgi?component=Trace-cmd%2FKernelshark&product=Tools&resolution=---
>
> I hope I am not disturbing your holidays. :)
>
Nah, but I wont be fixing it until next year. Happy Holidays!
-- Steve
prev parent reply other threads:[~2020-12-24 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 16:36 libtracefs documentation install problem Sudip Mukherjee
2020-12-24 17:23 ` Steven Rostedt [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=20201224122316.357b4538@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
/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).