From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/1] openssl: openssl-bin requires openssl-conf to run
Date: Thu, 16 Jul 2020 15:05:27 +0100 [thread overview]
Message-ID: <a5a2f620b4203f3c4584c7d686f4991ed5e3464c.camel@linuxfoundation.org> (raw)
In-Reply-To: <3541ef9cd5a1ebdfa20e9bfe1b1dacf4589bf2fd.1594897729.git.liezhi.yang@windriver.com>
On Thu, 2020-07-16 at 04:09 -0700, Robert Yang wrote:
> Fixed:
> $ dnf install openssl-bin
> $ openssl req -new -x509 -keyout lighttpd.pem -out lighttpd.pem -days
> 365 -nodes -batch
> Can't open /usr/lib/ssl-1.1/openssl.cnf for reading, No such file or
> directory
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> meta/recipes-connectivity/openssl/openssl_1.1.1g.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1g.bb
> b/meta/recipes-connectivity/openssl/openssl_1.1.1g.bb
> index 47ed6b7640..815955837b 100644
> --- a/meta/recipes-connectivity/openssl/openssl_1.1.1g.bb
> +++ b/meta/recipes-connectivity/openssl/openssl_1.1.1g.bb
> @@ -204,6 +204,8 @@ CONFFILES_openssl-conf =
> "${sysconfdir}/ssl/openssl.cnf"
> RRECOMMENDS_libcrypto += "openssl-conf"
> RDEPENDS_${PN}-ptest += "openssl-bin perl perl-modules bash"
>
> +RDEPENDS_${PN}-bin += "openssl-conf"
> +
> BBCLASSEXTEND = "native nativesdk"
Wasn't this addressed by:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=cd80b0e52ee2e008672ce910856f63176bc00480
?
Cheers,
Richard
next prev parent reply other threads:[~2020-07-16 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 11:09 [PATCH 0/1] openssl: openssl-bin requires openssl-conf to run Robert Yang
2020-07-16 11:09 ` [PATCH 1/1] " Robert Yang
2020-07-16 14:05 ` Richard Purdie [this message]
2020-07-17 2:01 ` [OE-core] " Robert Yang
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=a5a2f620b4203f3c4584c7d686f4991ed5e3464c.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.