From: Jose Quaresma <quaresma.jose@gmail.com>
To: Fathi Boudra <fathi.boudra@linaro.org>, Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] [oe][meta-filesystem][PATCH v2] composefs: add a new recipe
Date: Tue, 9 Apr 2024 11:28:36 +0100 [thread overview]
Message-ID: <CANPvuRmVFx5h17D7USiE3UR8=HEELORxvZ9UTao4Y4hof38VOg@mail.gmail.com> (raw)
In-Reply-To: <CAGNsrLDn+pyjP9SQA=Pb5ybHtQrkBNphO=mCK5htBV=T1hGs0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
Fathi Boudra <fathi.boudra@linaro.org> escreveu (terça, 9/04/2024 à(s)
11:09):
> Hi José,
>
> On Tue, 9 Apr 2024 at 12:00, Jose Quaresma <quaresma.jose@gmail.com>
> wrote:
> > Hi Fathi,
> >
> > Maybe just the #include <libgen.h> can do the job.
> >
> > It includes the posix implementation of the basename
> > https://man7.org/linux/man-pages/man0/libgen.h.0p.html
> >
> > Added the same comment on the github PR.
> >
> > Jose
>
> I tried it initially. It looks like we need to use the gnu
> implementation in this case, not the posix one (including libgen.h
> won't be enough). Hence, I ended to propose the approach used in kmod.
>
Ok, understand.
My suggestion was mainly because I saw several patches on the Khem branch.
Thanks for the clarification.
> Though, as many projects are affected and we can find several patches
> floating around to fix the musl basename function changes, I wonder if
> we should go down the road to include a stub in musl. I think that's
> what alpine proposed at some point.
>
Seems like a good plan but I didn't find references about this problem on
the musl mailing list.
--
Best regards,
José Quaresma
[-- Attachment #2: Type: text/html, Size: 2101 bytes --]
prev parent reply other threads:[~2024-04-09 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 7:54 [PATCH] [oe][meta-filesystem][PATCH v2] composefs: add a new recipe Fathi Boudra
2024-04-09 10:00 ` Jose Quaresma
2024-04-09 10:09 ` Fathi Boudra
2024-04-09 10:28 ` Jose Quaresma [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='CANPvuRmVFx5h17D7USiE3UR8=HEELORxvZ9UTao4Y4hof38VOg@mail.gmail.com' \
--to=quaresma.jose@gmail.com \
--cc=fathi.boudra@linaro.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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.
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).