From: "Yang Xu (徐扬)" <Yang.Xu@mediatek.com>
To: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"alex.kanavin@gmail.com" <alex.kanavin@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] openssl: set package level PERL5LIB
Date: Tue, 25 Apr 2023 06:00:47 +0000 [thread overview]
Message-ID: <2a1a3752a13396f7a0bc78cb1321913a4f16b1f9.camel@mediatek.com> (raw)
In-Reply-To: <db555f3f6c09c4576358846cba9e64d055422e59.camel@linuxfoundation.org>
Dear Sirs,
Sorry, please NOT accept this patch because I found it will break its
own sstate cache.
I will found other solution for this openssl/perl co-work issue.
On Thu, 2023-04-20 at 21:11 +0100, Richard Purdie wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
>
> On Thu, 2023-04-20 at 19:20 +0200, Alexander Kanavin wrote:
> > Thank you, I understand this now. I'm fine with the fix, but can
> > you
> > add this additional information to the commit message? So that it's
> > available in git history if anyone needs to understand it.
>
> I think there is something additional we need to do. If the path
> compiled into perl breaks when it is installed from sstate, we should
> make sure this path is *always* incorrect. That way things will work
> or
> fail deterministicly.
>
> Cheers,
>
> Richard
prev parent reply other threads:[~2023-04-25 6:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 5:24 [PATCH] openssl: set package level PERL5LIB Yang Xu
2023-04-20 9:22 ` Alexander Kanavin
2023-04-20 13:42 ` Yang Xu (徐扬)
2023-04-20 17:20 ` Alexander Kanavin
2023-04-20 20:11 ` [OE-core] " Richard Purdie
2023-04-21 3:03 ` Yang Xu
2023-04-21 6:54 ` [OE-core] " Alexander Kanavin
[not found] ` <1757E0BF64FE2869.29498@lists.openembedded.org>
2023-04-21 10:09 ` Alexander Kanavin
2023-04-25 6:00 ` Yang Xu (徐扬) [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=2a1a3752a13396f7a0bc78cb1321913a4f16b1f9.camel@mediatek.com \
--to=yang.xu@mediatek.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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: 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