From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: linux-trace-devel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH v4] libtraceevent: Add initial support for meson
Date: Sat, 24 Dec 2022 14:16:20 -0500 [thread overview]
Message-ID: <20221224141620.5f44a6fb@rorschach.local.home> (raw)
In-Reply-To: <20221224153225.ojre2c3fxktfxtj2@carbon.lan>
On Sat, 24 Dec 2022 16:32:25 +0100
Daniel Wagner <dwagner@suse.de> wrote:
> During my packaging attempt I found out that the man pages are installed
> into subdirs. So I started to look into the this and ... let's say it's
> complicated.
Oh, to make your life easier. That shouldn't happen.
>
> For example libtraceevent-func_apis.txt list a few function which are
> also listed in libtraceevent-func_find.txt. The Makefile uses these
> function as build names but, if we have two targets with the same name
> one will overwrite the other. make seems to tolerate something like
> this. Meson doesn't.
That's actually a mistake :-/
The asciidoc complains whenever a man page has more than 9 functions
described, so I have to break them up when I add more related APIs.
I probably missed removing some of the old functions when I did that
here.
>
> I am playing with various ideas how we could handle this. Currently, I
> think the best way is to distinguish the different source txt files. So
> we have files which are for generating a mans per function (1:n)
> and we have txt files which are general documentation (1:1).
The real fix is to remove the tep_find_function() and
tep_find_function_address() from libtraceevent-func_apis.txt.
-- Steve
next prev parent reply other threads:[~2022-12-24 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 18:08 [PATCH v4] libtraceevent: Add initial support for meson Daniel Wagner
2022-12-24 15:32 ` Daniel Wagner
2022-12-24 19:16 ` Steven Rostedt [this message]
2022-12-27 7:34 ` 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=20221224141620.5f44a6fb@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=dwagner@suse.de \
--cc=linux-trace-devel@vger.kernel.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).