From: Hongxu Jia <hongxu.jia@windriver.com>
To: <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] openssl: use nativeperl to build
Date: Fri, 12 Oct 2018 17:26:00 +0800 [thread overview]
Message-ID: <c1f23152-78db-f42d-becc-435cd777fee4@windriver.com> (raw)
In-Reply-To: <d79efe64-c2a1-fb09-d174-7d27ab741442@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 2061 bytes --]
On 2018年10月12日 17:03, Hongxu Jia wrote:
>> https://github.com/openssl/openssl/commit/4e351ca92e3a1f447cef3d2e330f13941f9412c6
>>
>> That is a good find. Perhaps we could check for that in sanity.bbclass?
>> Is it commonly available in distributions like centos?
> I am afraid the perl module (Text::Template) is not common,
> available on most distro, since they do not need to build
> openssl :(
>
> But I am curious that without that perl module, the build seem
> ok with newer perl (perl v5.22.1 in ubuntu 1804 and without
> Text::Template)
>
> I am going on digging the root cause why the build works well
> without the perl module
>
I know the reason
It will try to use Text::Template, if failed it fallback to load the old
one in perl source
[snip util/dofile.pl]
use with_fallback "Text::Template 1.46";
[snip util/dofile.pl]
[snip util/perl/with_fallback.pm]
sub import {
shift;
use File::Basename;
use File::Spec::Functions;
foreach (@_) {
eval "use $_";
if ($@) {
unshift @INC, catdir(dirname(__FILE__),
"..", "..", "external", "perl");
my $transfer = "transfer::$_";
eval "use $transfer";
shift @INC;
warn $@ if $@;
}
}
}
[snip util/perl/with_fallback.pm]
https://github.com/openssl/openssl/commit/8ff2af548303d311ce3591406111f77862875a60
[comments]
Bundle the non core Perl module Text::Template
Because we're using Text::Template and we know it's a non core Perl
module, we choose to bundle it into our source, for convenience.
external/perl/Downloaded.txt document what modules we choose to bundle
this way and exactly where we downloaded it from.
With this changes comes the transfer module for with_fallback.
Reviewed-by: Rich Salz <rsalz@openssl.org>
[comments]
//Hongxu
> //Hongxu
[-- Attachment #2: Type: text/html, Size: 3547 bytes --]
prev parent reply other threads:[~2018-10-12 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 9:55 [PATCH] openssl: use nativeperl to build Hongxu Jia
2018-10-11 12:00 ` richard.purdie
2018-10-11 14:58 ` Hongxu Jia
2018-10-12 7:54 ` Hongxu Jia
2018-10-12 8:57 ` richard.purdie
2018-10-12 9:03 ` Hongxu Jia
2018-10-12 9:26 ` Hongxu Jia [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=c1f23152-78db-f42d-becc-435cd777fee4@windriver.com \
--to=hongxu.jia@windriver.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