From: "Érico Nogueira" <ericonr@disroot.org>
To: "Mark Wielaard" <mark@klomp.org>, <elfutils-devel@sourceware.org>,
<musl@lists.openwall.com>
Cc: "Érico Rolim" <erico.erc@gmail.com>
Subject: [musl] Re: [QUESTION] Which fnmatch() functionality does elfutils depend on?
Date: Mon, 26 Oct 2020 14:28:59 -0300 [thread overview]
Message-ID: <C6N00TCRSZ1Q.2N2OVNTROUQHZ@mussels> (raw)
In-Reply-To: <723b967389be88475206c5afc280c3be02ab677c.camel@klomp.org>
On Mon Oct 26, 2020 at 3:10 PM -03, Mark Wielaard wrote:
> Hi Érico,
>
> On Mon, 2020-10-26 at 12:03 -0300, Érico Nogueira via Elfutils-devel
> wrote:
> > Do elfutils program actually depend on the extra functionality
> > enabled by
> > FNM_EXTMATCH? Is changing the flag to have no effect a "bug"?
>
> Yes. The extended wildcard pattern is relied upon by both
> eu-strip with
>
> --keep-section=SECTION Keep the named section. SECTION is an
> extended wildcard pattern. May be given
> more than once.
>
> and eu-elfcompress with
>
> -n, --name=SECTION SECTION name to (de)compress, SECTION is an
> extended wildcard pattern (defaults to
> '.?(z)debug*')
>
> In the eu-strip case it might be reasoned that instead of a
> wildcard pattern the user might most of the time simply provide
> a section name as is (especially since the option may be given
> multiple times). But in the case of eu-elfcompress the
> program relies on the default SECTION name being an extended
> wildcard pattern. So not supporting FNM_EXTMATCH breaks the
> default functionality of eu-elfcompress.
>
> Cheers,
>
> Mark
Understood, thank you. I'm replying to the musl mailing list as well,
then, to hopefully gather more opinions, since I don't know what the
best way of solving this would be.
Thanks,
Érico
next parent reply other threads:[~2020-10-26 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <723b967389be88475206c5afc280c3be02ab677c.camel@klomp.org>
2020-10-26 17:28 ` Érico Nogueira [this message]
2020-10-26 17:54 ` Max Rees
2020-10-26 22:32 ` Mark Wielaard
2020-10-26 23:25 ` Rich Felker
2020-10-27 9:19 ` Florian Weimer
2020-10-27 15:04 ` Mark Wielaard
2020-10-27 17:08 ` Rich Felker
2020-10-27 22:19 ` Mark Wielaard
2020-10-27 22:25 ` Rich Felker
2020-10-28 10:05 ` Mark Wielaard
2020-10-28 14:03 ` Rich Felker
2020-10-26 19:55 ` Rich Felker
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=C6N00TCRSZ1Q.2N2OVNTROUQHZ@mussels \
--to=ericonr@disroot.org \
--cc=elfutils-devel@sourceware.org \
--cc=erico.erc@gmail.com \
--cc=mark@klomp.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).