From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: 54728@debbugs.gnu.org, ludo@gnu.org, maximedevos@telenet.be
Subject: bug#54728: [PATCH v2 2/2] gnu: valgrind: fix ld.so symbols not found
Date: Fri, 6 May 2022 22:16:22 +0200 [thread overview]
Message-ID: <20220506221622.6a49ac7c@primarylaptop.localdomain> (raw)
In-Reply-To: <20220427003717.7106b97a@primary_laptop>
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
Hi,
Did you manage to receive the patches, or were they lost somehow[1]?
At least I see them on https://issues.guix.gnu.org/54728 .
References:
-----------
[1]Personally for some reason I didn't receive a copy of the patches I
sent through git-send-email in my mail.
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-05-06 20:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 15:01 bug#54728: Valgrind not working out of the box due to stripped ld.so Denis 'GNUtoo' Carikli
2022-04-07 16:40 ` Ludovic Courtès
2022-04-14 23:26 ` Denis 'GNUtoo' Carikli
2022-04-14 23:30 ` bug#54728: [PATCH 1/2] gnu: valgrind: impots: sort imports alphabetically Denis 'GNUtoo' Carikli
2022-04-14 23:30 ` bug#54728: [PATCH 2/2] gnu: valgrind: fix ld.so symbols not found Denis 'GNUtoo' Carikli
2022-04-15 16:21 ` Ludovic Courtès
2022-04-25 16:39 ` Denis 'GNUtoo' Carikli
2022-04-25 17:41 ` Maxime Devos
2022-04-26 1:39 ` Denis 'GNUtoo' Carikli
2022-04-26 1:39 ` bug#54728: [PATCH v2 1/2] gnu: valgrind: impots: sort imports alphabetically Denis 'GNUtoo' Carikli
2022-04-26 1:39 ` bug#54728: [PATCH v2 2/2] gnu: valgrind: fix ld.so symbols not found Denis 'GNUtoo' Carikli
2022-04-26 22:37 ` Denis 'GNUtoo' Carikli
2022-05-06 20:16 ` Denis 'GNUtoo' Carikli [this message]
2022-05-06 20:20 ` Maxime Devos
2022-05-09 9:24 ` bug#54728: Valgrind not working out of the box due to stripped ld.so Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220506221622.6a49ac7c@primarylaptop.localdomain \
--to=gnutoo@cyberdimension.org \
--cc=54728@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).