Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Watt <jpewhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] openssl: Fix documentation DEPENDS
Date: Thu, 27 Jun 2019 08:55:39 -0500	[thread overview]
Message-ID: <20190627135539.16014-1-JPEWhacker@gmail.com> (raw)

perl is required to generate the OpenSSL documentation, and therefore
should be present at do_compile. If not, OpenSSL will skip the
documentation generation, which isn't reproducible

Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
 meta/recipes-connectivity/openssl/openssl_1.1.1c.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb b/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb
index 01174073167..c57626d8f6d 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1c.bb
@@ -10,6 +10,8 @@ LICENSE = "openssl"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=d343e62fc9c833710bbbed25f27364c8"
 
 DEPENDS = "hostperl-runtime-native"
+# Perl is required to generate documentation
+DEPENDS_append_class-target = " perl-native"
 
 SRC_URI = "http://www.openssl.org/source/openssl-${PV}.tar.gz \
            file://run-ptest \
-- 
2.21.0



             reply	other threads:[~2019-06-27 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 13:55 Joshua Watt [this message]
2019-06-27 16:20 ` [PATCH] openssl: Fix documentation DEPENDS Burton, Ross
  -- strict thread matches above, loose matches on Subject: below --
2019-08-27 12:46 Joshua Watt
2019-08-27 12:56 ` Alexander Kanavin
2019-08-27 13:08   ` Joshua Watt
2019-08-27 13:25     ` Alexander Kanavin
2019-08-27 16:12       ` Joshua Watt
2019-08-27 16:16         ` Alexander Kanavin
2019-08-27 16:41           ` Richard Purdie

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=20190627135539.16014-1-JPEWhacker@gmail.com \
    --to=jpewhacker@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox