public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/31892] Always install mtrace. Date: Thu, 20 Jun 2024 08:33:29 +0000 [thread overview] Message-ID: <bug-31892-131-MV8Z8aKD9x@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31892-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31892 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.40 Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Florian Weimer <fweimer at redhat dot com> --- Fixed for 2.40 via: commit 086910fc41655152812b515dc324d2ac0dc36e67 Author: Florian Weimer <fweimer@redhat.com> Date: Thu Jun 20 10:32:16 2024 +0200 malloc: Always install mtrace (bug 31892) Generation of the Perl script does not depend on Perl, so we can always install it even if $(PERL) is not set during the build. Change the malloc/mtrace.pl text substition not to rely on $(PERL). Instead use PATH at run time to find the Perl interpreter. The Perl interpreter cannot execute directly a script that starts with “#! /bin/sh”: it always executes it with /bin/sh. There is no perl command line switch to disable this behavior. Instead, use the Perl require function to execute the script. The additional shift calls remove the “.” shell arguments. Perl interprets the “.” as a string concatenation operator, making the expression syntactically valid. Reviewed-by: Carlos O'Donell <carlos@redhat.com> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-20 8:33 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-13 17:17 [Bug build/31892] New: " carlos at redhat dot com 2024-06-13 18:44 ` [Bug build/31892] " jsm28 at gcc dot gnu.org 2024-06-13 19:06 ` carlos at redhat dot com 2024-06-14 10:09 ` fweimer at redhat dot com 2024-06-14 16:02 ` carlos at redhat dot com 2024-06-14 16:03 ` carlos at redhat dot com 2024-06-14 16:14 ` fweimer at redhat dot com 2024-06-20 8:33 ` fweimer at redhat dot com [this message] 2024-06-20 9:18 ` schwab@linux-m68k.org 2024-06-21 11:15 ` fweimer at redhat 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-31892-131-MV8Z8aKD9x@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).