[arch-commits] Commit in valgrind/trunk (PKGBUILD)

[Frederik Schwan]

    Date: Friday, May 13, 2022 @ 15:25:31
  Author: freswa
Revision: 445405

glibc move from partially stripping to debug pkg

Valgrind supports debuginfod since 3.17.0. But it requires 
the debug symbols to be available on check(). This commit 
implements a workaround to only run the check function when 
the debug symbols are present. If not, a warning is shown. 
Also the process of building is documented on the top of 
the PKGBUILD.

Modified:
  valgrind/trunk/PKGBUILD

----------+
 PKGBUILD |   15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

Modified: PKGBUILD
===================================================================
--- PKGBUILD	2022-05-13 15:23:25 UTC (rev 445404)
+++ PKGBUILD	2022-05-13 15:25:31 UTC (rev 445405)
@@ -2,9 +2,19 @@
 # Contributor: Dan McGee <dan at archlinux.org>
 # Contributor: Allan McRae <allan at archlinux.org>
 
+# README
+# this package requires glibc-debug to run the check() function
+# as -debug packages are not available in [core], it has to be applied manually
+# whenever the tests shall run
+#
+# For a fresh build:
+# $repo-x86_64-build -- -I ../../glibc/trunk/glibc-debug*.pkg.tar.zst
+# $repo-x86_64-build
+# ${repo}pkg
+
 pkgname=valgrind
 pkgver=3.19.0
-pkgrel=1
+pkgrel=2
 pkgdesc='Tool to help find memory-management problems in programs'
 arch=('x86_64')
 license=('GPL')
@@ -57,6 +67,9 @@
 }
 
 check() {
+  # only run if glibc-debug is supplied manually
+  if ! pacman -Q glibc-debug; then echo -e "\033[1;31mcheck() not run, supply glibc-debug if unintended!\033[0m"; return 0; fi
+
   cd valgrind-${pkgver}
 
   # Make sure a basic binary runs. There should be no errors.