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 07:59:58 +0000	[thread overview]
Message-ID: <bug-14501-163-ij7BumohYa@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 #3 from Sreedhar Mahadevan <sreedharmahadevan@gmail.com> ---
Would like to update one development from my end. I cloned the lttng-modules
package directly from its Github repository:
https://github.com/lttng/lttng-modules

From this lttng-modules environment, I tried building lttng-modules v2.13.0
based on the instructions in its README.md file by referencing the custom linux
version that I was using (v5.10.x corresponding to Buildroot v2021.05) and it
built successfully. When I tried building lttng-modules v2.12.0 and v2.11.0 and
I got the exact error which I encountered in the Buildroot environment
(reported earlier in this bug report). I see that buildroot v2021.08 and
2021.11 all continue using lttng-modules v2.11.0 and all seem to have the same
issue. 

Is this possibly the reason for the issue? If yes, how do I solve it? I tried
hacking into the buildroot/package/lttng-modules/lttng-modules.mk and
lttng-modules.hash files but I still faced issues with the wrong sha256 hashes.
Can you please help?

-- 
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  8:00 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 [this message]
2022-01-06 17:52 ` bugzilla
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-ij7BumohYa@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.