All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Dario Faggioli <dfaggioli@suse.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] Fix `make -jN trace-cmd gui`
Date: Thu, 19 Nov 2020 22:09:10 -0500	[thread overview]
Message-ID: <20201119220910.1a8ec625@oasis.local.home> (raw)
In-Reply-To: <160564780533.18208.2518938894299815863.stgit@toolbox-dario-user-work>

On Tue, 17 Nov 2020 21:16:45 +0000
Dario Faggioli <dfaggioli@suse.com> wrote:

> Doing `make -j8 trace-cmd gui` fails like this:
> 
>   CMake Error at build/FindTraceCmd.cmake:110 (MESSAGE):
> 
>     Could not find libtraceevent!
> 
>   Call Stack (most recent call first):
>     CMakeLists.txt:24 (include)
> 
> Or like this:
> 
>   CMake Error at build/FindTraceCmd.cmake:64 (MESSAGE):
> 
>     Could not find trace-cmd!
> 
>   Call Stack (most recent call first):
>     CMakeLists.txt:20 (include)
> 
> That's because we need `trace-cmd` to have finished
> building before starting to build `gui`.
> 
> Signed-off-by: Dario Faggioli <dfaggioli@suse.com>

Thanks Dario,

I applied it. But note, we will be releasing kernelshark soon in its
own repository (a new and improved version!)

Stay tuned!

-- Steve

  reply	other threads:[~2020-11-20  3:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 21:16 [PATCH] Fix `make -jN trace-cmd gui` Dario Faggioli
2020-11-20  3:09 ` Steven Rostedt [this message]
2020-11-20 12:06   ` Dario Faggioli
2020-11-20 12:32     ` Yordan Karadzhov (VMware)
2020-11-20 13:43       ` Accuracy of traces sync [Was: Re: [PATCH] Fix `make -jN trace-cmd gui`] Dario Faggioli
2020-11-20 14:08         ` Steven Rostedt
2020-11-26  0:15           ` Dario Faggioli
2020-11-26  3:53             ` Tzvetomir Stoyanov

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=20201119220910.1a8ec625@oasis.local.home \
    --to=rostedt@goodmis.org \
    --cc=dfaggioli@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.