From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v7 0/2] Add initial support for meson
Date: Fri, 10 Feb 2023 16:47:44 -0500 [thread overview]
Message-ID: <20230210164744.53f1073d@gandalf.local.home> (raw)
In-Reply-To: <20230209093805.rg4sc3652in7smok@carbon.lan>
On Thu, 9 Feb 2023 10:38:05 +0100
Daniel Wagner <dwagner@suse.de> wrote:
> On Wed, Feb 08, 2023 at 10:12:02AM +0100, Daniel Wagner wrote:
> > The libtracecmd.pc didn't list the subdir 'trace-cmd' which caused
> > our kernelshard builds to fail.
>
> FWIW, I've updated the Tumbleweed packages (libtraceevent, libtracefs,
> libtracecmd, trace-cmd) to build with Meson and everything looks good now. As
> indicated there was only small fallout in our kernelshark build but that is now
> fixed with this latest version of these patches here. So all v7 of the patches
> are also properly tested in a productive environment.
>
> All these changes don't touch the existing Makefiles, so there is zero chance
> that existing build setups break with adding the Meson build files. Obviously,
> there will be additional work to keep both builds working, though I don't expect
> it should be much after this initial work to get it going.
>
> Steven, any chance you are going to apply them any time soon?
I'll take a look. Sorry I didn't get to it on my trip (other things came
up). Also, I'm still recovering from the flu now :-p
-- Steve
next prev parent reply other threads:[~2023-02-10 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 9:12 [PATCH v7 0/2] Add initial support for meson Daniel Wagner
2023-02-08 9:12 ` [PATCH v7 1/2] libtracecmd: " Daniel Wagner
2023-02-08 9:12 ` [PATCH v7 2/2] trace-cmd: " Daniel Wagner
2023-02-09 9:38 ` [PATCH v7 0/2] " Daniel Wagner
2023-02-10 21:47 ` Steven Rostedt [this message]
2023-02-13 7:54 ` 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=20230210164744.53f1073d@gandalf.local.home \
--to=rostedt@goodmis.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).