[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201012151732.6e439886@gandalf.local.home>
Date: Mon, 12 Oct 2020 15:17:32 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Tony Jones <tonyj@...e.de>
Cc: Jiri Olsa <jolsa@...hat.com>, LKML <linux-kernel@...r.kernel.org>,
Linux Trace Devel <linux-trace-devel@...r.kernel.org>,
Zamir SUN <sztsian@...il.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
zsun@...hat.com, Vitaly Chikunov <vt@...linux.org>,
Tzvetomir Stoyanov <tstoyanov@...are.com>,
Yordan Karadzhov <ykaradzhov@...are.com>,
Ben Hutchings <ben@...adent.org.uk>,
Sudip Mukherjee <sudipm.mukherjee@...il.com>,
John Kacur <jkacur@...hat.com>,
Clark Williams <williams@...hat.com>,
Al Stone <ahs3@...ian.org>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Subject: Re: [ANNOUNCE] libtraceevent.git
[ Removing the powertop mailing list because it's rejecting everything ]
On Mon, 12 Oct 2020 11:41:20 -0700
Tony Jones <tonyj@...e.de> wrote:
> On Mon, Oct 12, 2020 at 11:19:50AM -0400, Steven Rostedt wrote:
>
> > Once it's shown that it works for all the package maintainers, I will tag
> > it which should create the tarballs automatically on the above link.
>
> Hi.
>
> It builds fine for me after manually creating the tarball from git.
> Once there is an official versioned tarball I'll push it into
> openSUSE.
>
> I presume some perf Makefile changes will be forthcoming to use it,
> rather than continuing to force build it out of TRACE_EVENT_DIR
>
Zamir found this issue with the Documentation man pages:
Note, I'm not sure the proper way to fix this. I think this is the last
issue I need to resolve before making the tag.
-- Steve
On Thu, 8 Oct 2020 17:50:19 +0800
Zamir SUN <sztsian@...il.com> wrote:
> Hi,
>
> When I try to compiling the document of libtraceevent with the fix I
> mentioned in [1] applied, make doc-install fails with errors like
>
> "/usr/bin/install: cannot stat 'libtraceevent-record_parse.3': No such
> file or directory"
>
> Checking the compiled documents I see a lot of tep_*.3 generated, and
> some libtraceevent_*.html. However no libtraceevent_*.3.
>
> $ ls Documentation/*3 | head
> Documentation/libtraceevent.3
> Documentation/tep_alloc.3
> Documentation/tep_clear_flag.3
> Documentation/tep_cmdline_pid.3
> Documentation/tep_data_comm_from_pid.3
> Documentation/tep_data_flags.3
> Documentation/tep_data_pid.3
> Documentation/tep_data_pid_from_comm.3
> Documentation/tep_data_preempt_count.3
> Documentation/tep_data_type.3
> ls Documentation/*html | head
> Documentation/libtraceevent-commands.html
> Documentation/libtraceevent-cpus.html
> Documentation/libtraceevent-endian_read.html
> Documentation/libtraceevent-event_find.html
> Documentation/libtraceevent-event_get.html
> Documentation/libtraceevent-event_list.html
> Documentation/libtraceevent-event_print.html
> Documentation/libtraceevent-field_find.html
> Documentation/libtraceevent-field_get_val.html
> Documentation/libtraceevent-field_print.html
>
> I also tried to port the Makefile from trace-cmd/Documentation to the
> document dir, and it still only generates tep_*.3 files, so I feel this
> is not the issue with the patch from [1].
>
> As for my local environment, I have xmlto and asciidoc installed[2], but
> not asciidoctor. I expect asciidoc could generate the documentations
> like what it did in trace-cmd before.
>
> Any idea if this is issue with my environment or it's something that
> need to be implemented in the Makefile?
>
Hi Zamir,
Thanks a lot for looking into this. I took your advice and reverted my
blind copy of the Makefiles, scripts and include headers, and instead
copied over their full history from the Linux kernel Tools directory.
You can see that update no (which now includes the utilities.mak as well).
Can you see if this patch fixes your current issue?
-- Steve
diff --git a/Documentation/Makefile b/Documentation/Makefile
index edb8623..3a981be 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -157,7 +157,7 @@ endif
do-install-man: man
$(call QUIET_INSTALL, Documentation-man) \
$(INSTALL) -d -m 755 $(DESTDIR)$(man3dir); \
- $(INSTALL) -m 644 $(DOC_MAN3) $(DESTDIR)$(man3dir);
+ $(INSTALL) -m 644 $(OUTPUT)*.3 $(DESTDIR)$(man3dir);
install-man: check-man-tools man do-install-man
Powered by blists - more mailing lists