From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Ross Burton <ross.burton@arm.com>
Cc: "ecordonnier@snap.com" <ecordonnier@snap.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] libxcrypt: fix hard-coded ".so" extension
Date: Fri, 9 Jun 2023 17:50:27 +0200 [thread overview]
Message-ID: <2023060915502700eeb2a1@mail.local> (raw)
In-Reply-To: <B5654344-F58D-4A5D-8AD7-668A866E9CD4@arm.com>
On 09/06/2023 15:19:12+0000, Ross Burton wrote:
> Probably just fell through a crack, I’ve queued it locally for testing.
>
It didn't apply cleanly on my master-next and I was waiting for things
to calm down to get back to it.
> Sorry about that!
>
> Ross
>
> > On 9 Jun 2023, at 10:37, Etienne Cordonnier via lists.openembedded.org <ecordonnier=snap.com@lists.openembedded.org> wrote:
> >
> > Hello,
> > is everything OK with the patch? Is there anything blocking a merge?
> >
> > On Fri, May 26, 2023 at 1:52 PM <ecordonnier@snap.com> wrote:
> > From: Etienne Cordonnier <ecordonnier@snap.com>
> >
> > 2 issues:
> > - the .so extension is hard-coded, and therefore the libxcryt package compiled with
> > meta-darwin is empty, because the dylib files are not contained in FILES_${PN}
> > - nothing actually produces a file libcrypt-*.so (the symlink file is libcrypt.so, without dash), thus
> > defining FILES:${PN} manually to contain libcrypt-*.so has no effect.
> >
> > Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
> > ---
> > meta/recipes-core/libxcrypt/libxcrypt.inc | 6 ------
> > 1 file changed, 6 deletions(-)
> >
> > diff --git a/meta/recipes-core/libxcrypt/libxcrypt.inc b/meta/recipes-core/libxcrypt/libxcrypt.inc
> > index 61b0381076..454a55d73d 100644
> > --- a/meta/recipes-core/libxcrypt/libxcrypt.inc
> > +++ b/meta/recipes-core/libxcrypt/libxcrypt.inc
> > @@ -17,12 +17,6 @@ SRC_URI += "file://fix_cflags_handling.patch"
> >
> > PROVIDES = "virtual/crypt"
> >
> > -FILES:${PN} = "${libdir}/libcrypt*.so.* \
> > - ${libdir}/libcrypt-*.so \
> > - ${libdir}/libowcrypt*.so.* \
> > - ${libdir}/libowcrypt-*.so \
> > -"
> > -
> > S = "${WORKDIR}/git"
> >
> > BUILD_CPPFLAGS = "-I${STAGING_INCDIR_NATIVE}"
> > --
> > 2.36.1.vfs.0.0
> >
> >
> >
> >
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#182559): https://lists.openembedded.org/g/openembedded-core/message/182559
> Mute This Topic: https://lists.openembedded.org/mt/99149665/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-06-09 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 11:51 [PATCH] libxcrypt: fix hard-coded ".so" extension Etienne Cordonnier
2023-06-09 9:37 ` Etienne Cordonnier
2023-06-09 15:19 ` [OE-core] " Ross Burton
2023-06-09 15:50 ` Alexandre Belloni [this message]
2023-06-26 17:12 ` Etienne Cordonnier
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=2023060915502700eeb2a1@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=ecordonnier@snap.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.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