From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] openssl: make OPENSSL_ENGINES match install path
Date: Wed, 25 Sep 2019 10:54:53 -0500 [thread overview]
Message-ID: <39e9c9c3-dc27-03da-2149-fe173e5680f9@kernel.crashing.org> (raw)
In-Reply-To: <20190925115259.26437-2-george.mccollister@gmail.com>
On 9/25/19 6:52 AM, George McCollister wrote:
> Set OPENSSL_ENGINES to the path where engines are actually installed.
>
> Signed-off-by: George McCollister <george.mccollister@gmail.com>
> ---
> meta/recipes-connectivity/openssl/openssl_1.1.1d.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1d.bb b/meta/recipes-connectivity/openssl/openssl_1.1.1d.bb
> index 072f727e0b..8819e19ec4 100644
> --- a/meta/recipes-connectivity/openssl/openssl_1.1.1d.bb
> +++ b/meta/recipes-connectivity/openssl/openssl_1.1.1d.bb
> @@ -148,7 +148,7 @@ do_install_append_class-native () {
> OPENSSL_CONF=${libdir}/ssl-1.1/openssl.cnf \
> SSL_CERT_DIR=${libdir}/ssl-1.1/certs \
> SSL_CERT_FILE=${libdir}/ssl-1.1/cert.pem \
> - OPENSSL_ENGINES=${libdir}/ssl-1.1/engines
> + OPENSSL_ENGINES=${libdir}/engines-1.1
Is this a bug in the openssl recipe (it's placing engines in the wrong place),
or a bug in the recipes providing acceleration engines and THEY are going into
the wrong place?
The ssl-1.1/engines makes more sense to me.. as /usr/lib/engines-1.1 obscures
that they are OpenSSL related.
--Mark
> }
>
> do_install_append_class-nativesdk () {
>
next prev parent reply other threads:[~2019-09-25 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 11:52 [PATCH 0/1] make OPENSSL_ENGINES match install path George McCollister
2019-09-25 11:52 ` [PATCH 1/1] openssl: " George McCollister
2019-09-25 15:54 ` Mark Hatle [this message]
2019-09-25 18:13 ` George McCollister
2019-09-25 18:34 ` Khem Raj
2019-09-25 21:30 ` George McCollister
2019-09-25 21:39 ` Khem Raj
2019-09-25 18:37 ` Andre McCurdy
2019-09-25 19:12 ` George McCollister
2019-09-25 19:25 ` Andre McCurdy
2019-10-25 20:16 ` George McCollister
2019-10-25 21:09 ` akuster808
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=39e9c9c3-dc27-03da-2149-fe173e5680f9@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.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