public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/31357] $(objpfx)tst-rtld-list-diagnostics.out rule doesn't work with test wrapper Date: Fri, 09 Feb 2024 15:29:10 +0000 [thread overview] Message-ID: <bug-31357-131-odIsFoQqhG@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31357-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31357 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Target Milestone|--- |2.40 --- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> --- Fixed by commit 15de3d17e1d9da5d38efb0a87a82efbc5bda732d Author: Florian Weimer <fweimer@redhat.com> Date: Fri Feb 9 16:16:08 2024 +0100 elf: Remove attempt at env handling in elf/tst-rtld-list-diagnostics.py Instead, let the system shell parse the whole thing and invoke the env command. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-02-09 15:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-09 0:05 [Bug dynamic-link/31357] New: Incorrect $(objpfx)tst-rtld-list-diagnostics.out rule hjl.tools at gmail dot com 2024-02-09 0:25 ` [Bug dynamic-link/31357] " hjl.tools at gmail dot com 2024-02-09 0:53 ` [Bug dynamic-link/31357] $(objpfx)tst-rtld-list-diagnostics.out rule doesn't work with test wrapper hjl.tools at gmail dot com 2024-02-09 2:33 ` hjl.tools at gmail dot com 2024-02-09 15:29 ` hjl.tools at gmail dot com [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=bug-31357-131-odIsFoQqhG@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).