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] Incorrect $(objpfx)tst-rtld-list-diagnostics.out rule Date: Fri, 09 Feb 2024 00:25:15 +0000 [thread overview] Message-ID: <bug-31357-131-kgAXh82KAd@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 ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com --- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> --- The problem is that tst-rtld-list-diagnostics.py doesn't handle test wrapper properly: python3 -B tst-rtld-list-diagnostics.py \ --manual=../manual/dynlink.texi \ "/export/build/gnu/tools-build/glibc-apx-sde/test-sde.sh env /export/build/gnu/tools-build/glibc-apx-sde/build-x86_64-linux/elf/ld-linux-x86-64.so.2 --list-diagnostics" tst-rtld-list-diagnostics.py tries to skip the unnecessary env, but it drops the test wrapper instead. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-09 0:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-09 0:05 [Bug dynamic-link/31357] New: " hjl.tools at gmail dot com 2024-02-09 0:25 ` hjl.tools at gmail dot com [this message] 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
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-kgAXh82KAd@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).