From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: libc-alpha@sourceware.org
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>, commit-hurd@gnu.org
Subject: [hurd,commited] malloc: Really fix tst-memalign-3 link against threads
Date: Tue, 2 May 2023 21:26:55 +0200 [thread overview]
Message-ID: <20230502192655.1342645-2-samuel.thibault@ens-lyon.org> (raw)
In-Reply-To: <20230502192655.1342645-1-samuel.thibault@ens-lyon.org>
All the tst malloc variants need the thread linking flags.
---
malloc/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/malloc/Makefile b/malloc/Makefile
index 41c4f33c2a..21c5a7c0d7 100644
--- a/malloc/Makefile
+++ b/malloc/Makefile
@@ -190,7 +190,6 @@ $(objpfx)tst-mallocfork2-malloc-hugetlb2: $(shared-thread-library)
$(objpfx)tst-mallocfork3-malloc-hugetlb2: $(shared-thread-library)
$(objpfx)tst-malloc-fork-deadlock-malloc-hugetlb2: $(shared-thread-library)
$(objpfx)tst-malloc-stats-cancellation-malloc-hugetlb2: $(shared-thread-library)
-$(objpfx)tst-memalign-3: $(shared-thread-library)
# These should be removed by `make clean'.
extra-objs = mcheck-init.o libmcheck.a
@@ -354,6 +353,8 @@ $(objpfx)tst-malloc-tcache-leak-malloc-hugetlb2: $(shared-thread-library)
$(objpfx)tst-malloc_info-malloc-hugetlb1: $(shared-thread-library)
$(objpfx)tst-malloc_info-malloc-hugetlb2: $(shared-thread-library)
$(objpfx)tst-memalign-3: $(shared-thread-library)
+$(objpfx)tst-memalign-3-malloc-hugetlb1: $(shared-thread-library)
+$(objpfx)tst-memalign-3-malloc-hugetlb2: $(shared-thread-library)
tst-compathooks-on-ENV = LD_PRELOAD=$(objpfx)libc_malloc_debug.so
tst-compathooks-on-mcheck-ENV = LD_PRELOAD=$(objpfx)libc_malloc_debug.so
--
2.39.2
prev parent reply other threads:[~2023-05-02 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 19:26 [hurd,commited] malloc: Fix " Samuel Thibault
2023-05-02 19:26 ` Samuel Thibault [this message]
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=20230502192655.1342645-2-samuel.thibault@ens-lyon.org \
--to=samuel.thibault@ens-lyon.org \
--cc=commit-hurd@gnu.org \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).