From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: "Clément Léger" <clement.leger@bootlin.com>,
"Philippe Proulx" <eeppeliteloop@gmail.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/lttng-modules: enable CONFIG_FTRACE in kernel configuration
Date: Mon, 14 Nov 2022 22:31:40 +0100 [thread overview]
Message-ID: <20221114223140.49169eef@windsurf> (raw)
In-Reply-To: <20221012202317.2898868-1-thomas.petazzoni@bootlin.com>
On Wed, 12 Oct 2022 22:23:16 +0200
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> The build of lttng-modules will fail if the kernel does not have
> CONFIG_TRACEPOINTS enabled. However, CONFIG_TRACEPOINTS is a
> prompt-less option, and the most generic option that does enable
> CONFIG_TRACEPOINTS is CONFIG_FTRACE.
>
> In addition, CONFIG_FTRACE will also enable CONFIG_STACKTRACE, which
> is needed on CPU architectures that don't provide the STACKWALK
> mechanism in the kernel, as is the case on ARM 32-bit for example.
>
> Therefore, let's enable CONFIG_FTRACE when building lttng-modules.
>
> Cc: Clément Léger <clement.leger@bootlin.com>
> Reported-by: Clément Léger <clement.leger@bootlin.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> package/lttng-modules/lttng-modules.mk | 1 +
> 1 file changed, 1 insertion(+)
Both applied to next!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-11-14 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 20:23 [Buildroot] [PATCH 1/2] package/lttng-modules: enable CONFIG_FTRACE in kernel configuration Thomas Petazzoni via buildroot
2022-10-12 20:23 ` [Buildroot] [PATCH 2/2] package/lttng-modules: bump to 2.13.7 Thomas Petazzoni via buildroot
2022-11-14 21:31 ` Thomas Petazzoni via buildroot [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=20221114223140.49169eef@windsurf \
--to=buildroot@buildroot.org \
--cc=clement.leger@bootlin.com \
--cc=eeppeliteloop@gmail.com \
--cc=thomas.petazzoni@bootlin.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