Github messages for voidlinux
 help / color / mirror / Atom feed
From: jnbr <jnbr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] valgrind: update to 3.18.1.
Date: Tue, 16 Nov 2021 20:45:05 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34104@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 908 bytes --]

There is a new pull request by jnbr against master on the void-packages repository

https://github.com/jnbr/void-packages valgrind
https://github.com/void-linux/void-packages/pull/34104

valgrind: update to 3.18.1.
#### Testing the changes
- I tested the changes in this PR: YES

#### Local build testing
- I built this PR locally for my native architecture, (aarch64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl


This superseeds #30380.
To address remarks from the old PR:
 - The musl.supp file is now upstream, no need to patch it in anymore.
 - armv6 was not supported by valgrind in the past, I could not find any hint that this changed. If the code generation in valgrind asumes armv7 patching the configure script likely won't be enough. 


A patch file from https://github.com/void-linux/void-packages/pull/34104.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-valgrind-34104.patch --]
[-- Type: text/x-diff, Size: 1096 bytes --]

From c9ba75f7c80bbf9114728879b2feed6f2bbe3ada Mon Sep 17 00:00:00 2001
From: Johannes Brechtmann <johannes.brechtmann@gmail.com>
Date: Tue, 16 Nov 2021 17:22:22 +0000
Subject: [PATCH] valgrind: update to 3.18.1.

---
 srcpkgs/valgrind/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/valgrind/template b/srcpkgs/valgrind/template
index 71f90795aa96..2ee2b25242e4 100644
--- a/srcpkgs/valgrind/template
+++ b/srcpkgs/valgrind/template
@@ -1,6 +1,6 @@
 # Template file for 'valgrind'
 pkgname=valgrind
-version=3.16.1
+version=3.18.1
 revision=1
 build_style=gnu-configure
 configure_args="--enable-tls --without-mpicc --enable-lto=yes"
@@ -12,7 +12,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-2.0-or-later"
 homepage="http://valgrind.org/"
 distfiles="https://sourceware.org/pub/${pkgname}/${pkgname}-${version}.tar.bz2"
-checksum=c91f3a2f7b02db0f3bc99479861656154d241d2fdb265614ba918cc6720a33ca
+checksum=00859aa13a772eddf7822225f4b46ee0d39afbe071d32778da4d99984081f7f5
 
 CFLAGS="-fno-stack-protector"
 CXXFLAGS="-fno-stack-protector"

             reply	other threads:[~2021-11-16 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 19:45 jnbr [this message]
2021-11-16 21:17 ` [PR PATCH] [Updated] " jnbr
2021-11-16 21:55 ` jnbr
2021-11-16 22:12 ` jnbr
2021-11-18 21:33 ` unspecd
2021-11-18 21:58 ` [PR PATCH] [Updated] " jnbr
2021-11-18 22:21 ` jnbr
2021-11-18 22:34 ` [PR PATCH] [Merged]: " jnbr

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34104@inbox.vuxu.org \
    --to=jnbr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).