public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "shane.slattery at embecosm dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/25127] elf/Makefile uses @ sed sentinal, breaks for build paths with @ Date: Thu, 24 Aug 2023 15:42:55 +0000 [thread overview] Message-ID: <bug-25127-131-Q0fghdDUSA@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25127-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25127 Shane Slattery <shane.slattery at embecosm dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shane.slattery at embecosm dot com --- Comment #2 from Shane Slattery <shane.slattery at embecosm dot com> --- I recently encountered this bug under the same circumstances as Nigel, via Jenkins concurrent builds. I have sent a patch that properly solves this bug, by escaping possible @'s in the path before it is used with sed later. See patch here: https://sourceware.org/pipermail/libc-alpha/2023-August/151100.html Comments are welcome! -- You are receiving this mail because: You are on the CC list for the bug.
parent reply other threads:[~2023-08-24 15:42 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <bug-25127-131@http.sourceware.org/bugzilla/>]
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-25127-131-Q0fghdDUSA@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).