All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14501] lttng-modules v2.11 package fails to build
Date: Thu, 06 Jan 2022 17:52:39 +0000	[thread overview]
Message-ID: <bug-14501-163-Cl8uPPi7Qe@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14501-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=14501

--- Comment #4 from Fabrice Fontaine <fontaine.fabrice@gmail.com> ---
From understanding, the issue is raised on kernel >= 5.6 and lttng-modules has
fixed this issue with
https://github.com/lttng/lttng-modules/commit/edfdcb685c3f56dde803244449f79ad7bed03798

But there is a lot of other commits needed to be able to build on newer kernels
so I think that a bump is indeed the best course of action.

You can find a patch here:
https://patchwork.ozlabs.org/project/buildroot/patch/20220106174949.1064731-1-fontaine.fabrice@gmail.com/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-01-06 17:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05  7:39 [Buildroot] [Bug 14501] New: lttng-modules v2.11 package fails to build bugzilla
2022-01-05 13:36 ` [Buildroot] [Bug 14501] " bugzilla
2022-01-05 15:58 ` bugzilla
2022-01-06  7:59 ` bugzilla
2022-01-06 17:52 ` bugzilla [this message]
2022-01-07 13:50 ` bugzilla
2022-01-07 19:39 ` bugzilla
2022-01-11 13:20 ` bugzilla

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=bug-14501-163-Cl8uPPi7Qe@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.