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
