Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: devin.buildroot@gmail.com
To: buildroot@buildroot.org
Cc: Philippe Proulx <eeppeliteloop@gmail.com>,
	Devin Steffler <devin.buildroot@gmail.com>
Subject: [Buildroot] [PATCH 1/3] package/lttng-modules: bump to version 2.13.17
Date: Sat, 22 Feb 2025 08:31:25 -0500	[thread overview]
Message-ID: <20250222133127.9445-1-devin.buildroot@gmail.com> (raw)

From: Devin Steffler <devin.buildroot@gmail.com>

The current lttng-modules that buildroot uses is 2.13.10.
That version of lttng-modules does not compile with any recent version of buildroot, including the following:
- latest stable release: 2024.11.2
- latest long term release: 2024.02.11
- master branch on github

There are many compiler errors, the first compiler error from the master branch is as follows:

/home/devin/buildroot_test/buildroot/output/build/lttng-modules-2.13.10/./src/../include/wrapper/uprobes.h:28:16: error: too few arguments to function ‘uprobe_register’
   28 |         return uprobe_register(inode, offset, uc);
      |                ^~~~~~~~~~~~~~~

When investigating a potential fix to make lttng-modules build again, it was discovered that
the compiler errors were already fixed in newer versions of lttng-modules.

A changelog for lttng-modules 2.13.17 can be found here:
https://git.lttng.org/?p=lttng-modules.git;a=blob_plain;f=ChangeLog;hb=da244107a5ffe304f61bb25974bc25c8df05f66b

I tested lttng-modules 2.13.17 with the master branch only and it compiles fine.

As a side note, there are newer versions of lttng-tools (2.13.14) and lttng-ust (2.13.8) as well.
I believe that these should be updated together as they are listed on the lttng.org website together.
However, the buildroot manual recommends a single patch for each package that's updated.
So I'm planning to submit two more patches later on for lttng-tools and lttng-ust.

This is my first time submitting a patch for buildroot.

Signed-off-by: Devin Steffler <devin.buildroot@gmail.com>
---
 package/lttng-modules/lttng-modules.hash | 6 +++---
 package/lttng-modules/lttng-modules.mk   | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/package/lttng-modules/lttng-modules.hash b/package/lttng-modules/lttng-modules.hash
index b14b488837..133765aaba 100644
--- a/package/lttng-modules/lttng-modules.hash
+++ b/package/lttng-modules/lttng-modules.hash
@@ -1,8 +1,8 @@
-# From https://lttng.org/files/lttng-modules/lttng-modules-2.13.10.tar.bz2.sha256
-sha256  13abfb1ac870711f0d0adfa88e53b17deb2e3052173715a260a6ef14aa45b0a7  lttng-modules-2.13.10.tar.bz2
+# From https://lttng.org/files/lttng-modules/lttng-modules-2.13.17.tar.bz2.sha256
+sha256  b0b23504150ae5c1fc6ee14e28d029518f61fe2ec5f17bb61c7941aa52bb6e65  lttng-modules-2.13.17.tar.bz2
 
 # Hash for license files
 sha256  d72921266bc8452a8789f8a04a82755373990d00b7e0b0f1a8edb8f854e94d1c  LICENSES/LGPL-2.1
 sha256  6841c85b94f9dab319356e3aaf9e969fcedad51d3aaadf665bf86f34f4186b62  LICENSES/GPL-2.0
 sha256  323c587d0ccf10e376f8bf9a7f31fb4ca6078105194b42e0b1e0ee2bc9bde71f  LICENSES/MIT
-sha256  0133d3c505f176845d7a8b4dcfe006ac615832c43c41e76fe3b365191bafca92  LICENSE
+sha256  dc47dc17b111f67f52549d4f9649aead142f84317b269ecce80deb1b64e7d023  LICENSE
diff --git a/package/lttng-modules/lttng-modules.mk b/package/lttng-modules/lttng-modules.mk
index d6f1e4114d..9da4f07387 100644
--- a/package/lttng-modules/lttng-modules.mk
+++ b/package/lttng-modules/lttng-modules.mk
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-LTTNG_MODULES_VERSION = 2.13.10
+LTTNG_MODULES_VERSION = 2.13.17
 LTTNG_MODULES_SITE = http://lttng.org/files/lttng-modules
 LTTNG_MODULES_SOURCE = lttng-modules-$(LTTNG_MODULES_VERSION).tar.bz2
 LTTNG_MODULES_LICENSE = LGPL-2.1/GPL-2.0 (kernel modules), MIT (lib/bitfield.h, lib/prio_heap/*)
-- 
2.43.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2025-02-22 13:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-22 13:31 devin.buildroot [this message]
2025-02-22 13:31 ` [Buildroot] [PATCH 2/3] package/lttng-tools: bump to version 2.13.14 devin.buildroot
2025-02-22 13:31 ` [Buildroot] [PATCH 3/3] package/lttng-libust: bump to version 2.13.8 devin.buildroot
     [not found] ` <20250222133127.9445-2-devin.buildroot__2127.52547101758$1740231125$gmane$org@gmail.com>
2025-11-15 16:50   ` [Buildroot] [PATCH 2/3] package/lttng-tools: bump to version 2.13.14 Bernd Kuhls
     [not found] ` <20250222133127.9445-3-devin.buildroot__20167.7431746916$1740231130$gmane$org@gmail.com>
2025-11-15 16:51   ` [Buildroot] [PATCH 3/3] package/lttng-libust: bump to version 2.13.8 Bernd Kuhls
     [not found] <20250222133127.9445-1-devin.buildroot__4022.45489401452$1740231121$gmane$org@gmail.com>
2025-11-15 16:50 ` [Buildroot] [PATCH 1/3] package/lttng-modules: bump to version 2.13.17 Bernd Kuhls

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=20250222133127.9445-1-devin.buildroot@gmail.com \
    --to=devin.buildroot@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=eeppeliteloop@gmail.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