From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Jean-Marc Chevalier <jean-marc.chevalier@polymtl.ca>,
lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] Compile modules on Centos Stream 9
Date: Thu, 20 Jun 2024 11:48:16 -0400 [thread overview]
Message-ID: <18dcf546-e7bf-44a4-b8ef-5ec5f109fa27@efficios.com> (raw)
In-Reply-To: <364622686.75839325.1718811716721.JavaMail.zimbra@polymtl.ca>
Hi Jean-Marc,
On 6/19/24 11:41 AM, Jean-Marc Chevalier via lttng-dev wrote:
> Hi,
>
> Is it possible to build the lttng modules againt Centos Stream 9
> kernels? I see these warnings at the top when attempting to compile:
>
> make[1]: Entering directory '/usr/src/kernels/5.14.0-452.el9.x86_64'
> /home/tmp/git/lttng-modules/src/probes/Kbuild:28: File ./mm/slab.h not
> found. Probe "kmem" is disabled. Use full kernel source tree to enable it.
> /home/tmp/git/lttng-modules/src/probes/Kbuild:79: File
> ./arch/x86/kvm/lapic.h not found. Probe "kvm" x86-specific is disabled.
> Use full kernel source tree to enable it.
> /home/tmp/git/lttng-modules/src/probes/Kbuild:181: Files ./mm/internal.h
> not found. Probe "compaction" is disabled. Use full kernel source tree
> to enable it.
> /home/tmp/git/lttng-modules/src/probes/Kbuild:190: Files ./fs/ext4/*.h
> not found. Probe "ext4" is disabled. Use full kernel source tree to
> enable it.
> /home/tmp/git/lttng-modules/src/probes/Kbuild:213: File
> ./drivers/base/regmap/trace.h not found. Probe "regmap" is disabled. Use
> full kernel source tree to enable it.
>
The message reads to use the full kernel source tree if you want to
enable those probes.
Those probes depend on internal headers, which are not shipped as part
of the public header packages e.g. kernel-headers.rpm.
One way to get the full source tree is to extract it from the kernel
source rpm, e.g.
https://mirror.stream.centos.org/9-stream/BaseOS/source/tree/Packages/kernel-5.14.0-452.el9.src.rpm
thanks,
kienan
> I tried with module versions 2.12.17 and 2.13.13 against the kernel
> 5.14.0-452.el9.x86_64 and I obtain this error:
>
> /home/tmp/git/lttng-modules/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6: error: conflicting types for 'trace_sched_stat_runtime'; have 'void(struct task_struct *, u64, u64)' {aka 'void(struct task_struct *, long long unsigned int, long long unsigned int)'}
>
> Any help would be greatly appreciated.
>
> - JM
>
> --
> - Jean-Marc Chevalier
> Technicien
> Génie informatique Génie logiciel
> Local: M-4002
> Téléphone: 514-340-4711 x4266
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2024-06-20 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 15:41 Jean-Marc Chevalier via lttng-dev
2024-06-20 15:26 ` Kienan Stewart via lttng-dev
2024-06-25 21:52 ` Jean-Marc Chevalier via lttng-dev
2024-06-20 15:48 ` Kienan Stewart via lttng-dev [this message]
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=18dcf546-e7bf-44a4-b8ef-5ec5f109fa27@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=jean-marc.chevalier@polymtl.ca \
--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