All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harkin <ryan.harkin@linaro.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: How to backport openssl to Sumo
Date: Wed, 20 Nov 2019 18:18:05 +0000	[thread overview]
Message-ID: <CAD0U-hKudOEYkkPQQ1He3=Cg1hLqT7u5Uhsn_e2ZK0vGmo+z3w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]

Hi all,

I'm struggling with backporting OpenSSL to my Sumo build [1], so wondered
if anyone else had done something similar with success.

I copied "meta/recipes-connectivity/openssl" from Poky master branch [2]
into my own layer [3]. It didn't pick up, so I discovered I needed to add
a PREFERRED_VERSION, eg:

+PREFERRED_VERSION_openssl ?= "1.1.%"
+PREFERRED_VERSION_openssl-native ?= "1.1.%"
+PREFERRED_VERSION_nativesdk-openssl ?= "1.1.%"

Now it builds fine. However, I no longer have /usr/bin/openssl in my disk
image.

It doesn't appear in FILES_${PN}, and adding it to the recipes doesn't seem
to make any difference.

What am I missing?

Thanks,
Ryan.

[1] I'm looking for CVE fixes, 1.0.2p has a lot of CVEs.

[2] http://git.yoctoproject.org/git/poky
I'm at SHA a616ffebdc, so I copied openssl_1.1.1d.bb and all the other
files in the directory.

[3] I have a clone of Linaro's meta-backports. I'm trying to generate a
patch to submit for review there.
https://git.linaro.org/openembedded/meta-backports.git

[-- Attachment #2: Type: text/html, Size: 1555 bytes --]

             reply	other threads:[~2019-11-20 18:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 18:18 Ryan Harkin [this message]
2019-11-20 18:28 ` How to backport openssl to Sumo Ross Burton
2019-11-20 18:59   ` Ryan Harkin
2019-11-20 18:36 ` Mark Hatle
2019-11-20 19:06   ` Ryan Harkin
2019-11-20 19:09     ` Mark Hatle
2019-11-20 19:27       ` Andre McCurdy
2019-11-20 19:44         ` Ryan Harkin
2019-11-20 19:57           ` Andre McCurdy
2019-11-20 21:29       ` Ryan Harkin
2019-11-20 22:41         ` Ryan Harkin
2019-11-20 23:53           ` Andre McCurdy
2019-11-21  8:05             ` Mikko.Rapeli
2019-11-22  1:12               ` Ross Burton
2019-11-21 13:15             ` Ryan Harkin
2019-11-21 13:38               ` Nicolas Dechesne
2019-11-21 13:53                 ` Ryan Harkin
2019-11-22  0:11                   ` Andre McCurdy
2019-11-20 21:39 ` Mikko.Rapeli
2019-11-20 23:05   ` Adrian Bunk
2019-11-21  8:01     ` Mikko.Rapeli

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='CAD0U-hKudOEYkkPQQ1He3=Cg1hLqT7u5Uhsn_e2ZK0vGmo+z3w@mail.gmail.com' \
    --to=ryan.harkin@linaro.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 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.