gentoo auto-resync : 10:01:2025 - 06:41:30

2 files changed, 0 insertions, 88 deletions

diff --git a/dev-util/lttng-tools/Manifest b/dev-util/lttng-tools/Manifest
index b0091c1a0fab..53ef7010ede5 100644
--- a/dev-util/lttng-tools/Manifest
+++ b/dev-util/lttng-tools/Manifest
@@ -1,4 +1,3 @@
-AUX lttng-tools-2.13.9-slibtool.patch 4024 BLAKE2B 38aae443574440c9efd3b895c55e7a2e482d0dc1ba27f0bddfe43170a5b1fc20b8be436ce31005bac71c33bf9c312197bde07f20a7e721426f2ed943309a5890 SHA512 186ec460c30de9696685769e0bdba8dcf5f55b13e0bbf1565f087f7ec5381cf4de90795d6fa703136ed0f06ab51931911f30518ff8c6088753d91323be20e3b2
 DIST lttng-tools-2.13.14.tar.bz2 1932238 BLAKE2B f079051502d01ffc67c4f8f0bbcdf3a4428546c652dcc352918c4908a37aeb510dd66309306cec835297c8d2f276e5cbd22ea4efef6866d3c0c0cf8651d68ef8 SHA512 61bdebb539cfb4eb61c9806e98742f39dc032d849b03d90cdb98d1891bd5bfbd0cb1f54bbc7bf79a11505ce7fee558497312d650bb41f11f739884e7cb8a750f
 EBUILD lttng-tools-2.13.14.ebuild 1119 BLAKE2B 0752f0394948e169dedff2ee32566722d252796c85b480c829811b8f938775ce2840890c6c51552df20e3710c3f9dda4d7584d791a3f69cfc765a2754f5e2b0b SHA512 c52acf814f49e699a6e3822c8c9d1f850cfcb63171049a427d53b6a52f096f205c266706116f1b87fa5f792fdd3bacd6f0a8062b6a51120a595816d4c5c9faaa
 MISC metadata.xml 573 BLAKE2B f09a37ebcb2f9dfac332d501ba1cab5ae68e51e1cc40903d7b4a7a09feb98b3c893add8a9dcdd47427b7e6bee1817e3c4376bfee9c6241208cd4c7e082a25408 SHA512 333ebb1393d309296ded2c15e331afcf0cf2c27be7b3963fb06875c39b5969e531bbce100d648ef23a4c46de2deb44e9d7372cb768378b162346a55e1d273018
diff --git a/dev-util/lttng-tools/files/lttng-tools-2.13.9-slibtool.patch b/dev-util/lttng-tools/files/lttng-tools-2.13.9-slibtool.patch
deleted file mode 100644
index 634bd388b44c..000000000000
--- a/dev-util/lttng-tools/files/lttng-tools-2.13.9-slibtool.patch
+++ /dev/null
@@ -1,87 +0,0 @@
-https://github.com/lttng/lttng-tools/pull/169
-https://github.com/lttng/lttng-tools/commit/bb1c9fc3f89c2faffb0228c0b77e32653e018a23
-
-From bb1c9fc3f89c2faffb0228c0b77e32653e018a23 Mon Sep 17 00:00:00 2001
-From: orbea <orbea@riseup.net>
-Date: Fri, 8 Mar 2024 08:17:37 -0800
-Subject: [PATCH] Fix: baddr-statedump: use $(LIBTOOL) --mode=execute
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-GNU libtool inconsistently places the compiled executable in the source
-directory or in the .libs directory where a libtool wrapper script is
-placed in the source directory.
-
-While slibtool will always place the compiled executable in the .libs
-directory and a wrapper script in the source directory.
-
-This will result with a build error when using slibtool since objcopy
-needs the executable and not the shell wrapper script, but this can be
-solved for both implementations by using $(LIBTOOL) --mode=execute on all
-commands that operate on the libtool compiled executables.
-
-Gentoo issue: https://bugs.gentoo.org/858095
-
-The GNU libtool --mode=excute is documented upstream.
-
-https://www.gnu.org/software/libtool/manual/html_node/Execute-mode.html
-https://www.gnu.org/software/libtool/manual/html_node/Debugging-executables.html
-
-And the GNU libtool behavior of when to create a wrapper script is
-documented in the 'Linking Executables' section.
-
-  "Notice that the executable, hell, was actually created in the .libs
-  subdirectory. Then, a wrapper script (or, on certain platforms, a
-  wrapper executable see Wrapper executables) was created in the current
-  directory.
-
-  Since libtool created a wrapper script, you should use libtool to
-  install it and debug it too. However, since the program does not depend
-  on any uninstalled libtool library, it is probably usable even without
-  the wrapper script."
-
-https://www.gnu.org/software/libtool/manual/html_node/Linking-executables.html
-
-And the inconsistency between GNU libtool and slibtool is documented at
-the Gentoo wiki.
-
-  "One difference between GNU libtool and slibtool is that the former will
-  conditionally place the compiled executable or a shell wrapper script in
-  the build directory, depending on whether or not the executable depends
-  on a build-local libtool library (e.g. libfoo.la). Where slibtool will
-  always place a compatible wrapper script in the build directory where
-  GNU libtool would have conditionally placed the executable. When the
-  wrapper script is created both GNU libtool and slibtool will place the
-  executable in the .libs directory within the build directory.
-  Consequently build systems, ebuilds, and other users should take care to
-  avoid scenarios like installing the wrapper script to the system instead
-  of the executable. In these cases ideally the executable would be
-  installed by the same libtool implementation that compiled it."
-
-https: //wiki.gentoo.org/wiki/Slibtool#Installing_or_using_binaries_created_by_libtool_manually
-Signed-off-by: orbea <orbea@riseup.net>
-Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
-Change-Id: I03102ed78af835daa9b9a5836c2979a5f5d4bd8c
----
- tests/regression/ust/baddr-statedump/Makefile.am | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/tests/regression/ust/baddr-statedump/Makefile.am b/tests/regression/ust/baddr-statedump/Makefile.am
-index f8fe26395..d37dbb6dd 100644
---- a/tests/regression/ust/baddr-statedump/Makefile.am
-+++ b/tests/regression/ust/baddr-statedump/Makefile.am
-@@ -19,11 +19,11 @@ EXTRA_DIST = test_baddr-statedump test_baddr-statedump.py
- 
- # Extract debug symbols
- prog.debug: prog
--	$(objcopy_verbose)$(OBJCOPY) --only-keep-debug prog prog.debug
-+	$(objcopy_verbose)$(LIBTOOL) --mode=execute $(OBJCOPY) --only-keep-debug prog prog.debug
- 
- # Strip and add debuglink
- prog.strip: prog.debug
--	@cp -f prog prog.strip
-+	@$(LIBTOOL) --mode=execute cp -f prog prog.strip
- 	$(objcopy_verbose)$(OBJCOPY) --strip-debug --add-gnu-debuglink=prog.debug prog.strip
- 
- all-local: prog.strip