From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org, David Aldrich <david.aldrich.ntml@gmail.com>
Subject: Re: How to build lttng on RHEL 9?
Date: Mon, 19 Jan 2026 12:02:44 -0500 [thread overview]
Message-ID: <c3a11b9b-5cd1-4a0c-b15c-d86a5f0d3924@efficios.com> (raw)
In-Reply-To: <CAJK_ieh7GpnMBe-J3ktiU4EmE2puqafgx4pmEBoJsbqKz9LEEA@mail.gmail.com>
Hi David,
RHEL kernels often backport a variety of changes. It is likely that
lttng-modules needs to be updated for the exact kernel you're building
for, which is usually just updating version range checks similar to this[1].
Based on your error message, I think the version range check that needs
to be updated is here[2].
What's the exact version number of the kernel you're trying to build for?
thanks,
kienan
[1]:
https://github.com/lttng/lttng-modules/commit/924b0ab5ad13570c4d4a305839684b37538064d7
[2]:
https://github.com/lttng/lttng-modules/blob/b1a23b9733ce6217659bc5e62961d128794a2beb/src/lttng-statedump-impl.c#L389
On 1/19/26 11:00 AM, David Aldrich via lttng-dev wrote:
> Hi
>
> I have a build error for lttng-modules-2.14.3 on RHEL 9.6:
>
> lttng-modules-2.14.3/src/lttng-statedump-impl.c:408:20: error:
> ‘dev_base_lock’ undeclared (first use in this function); did you mean
> ‘device_lock’?
> 408 | read_lock(&dev_base_lock);
> | ^~~~~~~~~~~~~
>
> Please can you advise me how to fix this?
>
> (I am only building from source because I assume lttng packages aren't
> available for RHEL 9).
>
> Thanks in advance
> David
next prev parent reply other threads:[~2026-01-19 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 16:00 David Aldrich via lttng-dev
2026-01-19 17:02 ` Kienan Stewart via lttng-dev [this message]
2026-01-19 17:14 ` David Aldrich via lttng-dev
2026-01-20 16:12 ` David Aldrich via lttng-dev
2026-01-21 15:21 ` Michael Jeanson via lttng-dev
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=c3a11b9b-5cd1-4a0c-b15c-d86a5f0d3924@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=david.aldrich.ntml@gmail.com \
--cc=kstewart@efficios.com \
/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