From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andreas Schwab <schwab@suse.de>,
Daniel Bristot de Oliveira <bristot@kernel.org>,
jianchunfu <jianchunfu@cmss.chinamobile.com>
Subject: Re: [GIT PULL] rtla: Updates for 5.20/6.0
Date: Fri, 5 Aug 2022 12:47:01 -0400 [thread overview]
Message-ID: <20220805124701.4b44195d@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wh+e1qcCnEYJ3JRDVLNCYbJ=0u+Ts5bOYZnY3mX_k-hFA@mail.gmail.com>
On Fri, 5 Aug 2022 09:40:25 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, Aug 3, 2022 at 7:49 AM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > Changes to RTLA:
>
> Btw, I note that the error messages for missing libraries got fixed
> (already some time ago, not this pull), but didn't get around to
> actually building until now.
>
> It says to do
>
> e.g., 'dnf install libtraceevent' on Fedora
>
> but it's actually the devel packages that are needed for building, not
> the bare libraries.
>
> So it should be libtraceevent-devel, and libtracefs-devel.
Thanks for the report (I obviously have them installed, and thus didn't see
this :-/). Not to mention, I always forget to add the -dev/-devel appendix
to my packages.
Daniel,
Can you send a fix?
Thanks!
-- Steve
next prev parent reply other threads:[~2022-08-05 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 14:49 Steven Rostedt
2022-08-05 16:40 ` Linus Torvalds
2022-08-05 16:47 ` Steven Rostedt [this message]
2022-08-06 13:01 ` Daniel Bristot de Oliveira
2022-08-06 15:52 ` Linus Torvalds
2022-08-06 18:06 ` John Kacur
2022-08-06 18:22 ` Steven Rostedt
2022-08-06 18:24 ` Linus Torvalds
2022-08-06 18:51 ` Steven Rostedt
2022-08-06 19:05 ` Linus Torvalds
2022-08-06 19:23 ` Steven Rostedt
2022-08-06 18:45 ` Steven Rostedt
2022-08-06 18:47 ` Steven Rostedt
2022-08-05 17:42 ` pr-tracker-bot
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=20220805124701.4b44195d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=jianchunfu@cmss.chinamobile.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwab@suse.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®