All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Jonathan Richardson <jonathan.richardson@broadcom.com>
Cc: poky@yoctoproject.org
Subject: Re: openssl10 in warrior
Date: Tue, 18 Jun 2019 23:29:56 +0200	[thread overview]
Message-ID: <20190618212956.GD1501@jama> (raw)
In-Reply-To: <e3607e3b603a3c19c520e59774b7039d@mail.gmail.com>

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

On Tue, Jun 18, 2019 at 01:29:00PM -0700, Jonathan Richardson wrote:
> Hello,
> 
> How do you set the version of openssl back to openssl10? There is no
> PROVIDES
> openssl in openssl10  so I can't set PREFERRED_PROVIDER_openssl. If I
> change my
> DEPENDS in the my recipe to openssl10-native  eventually another native
> recipe that
> depends on openssl tries to populate a library to sysroot and fails
> because its already
> there.

Hi,

it never worked with both openssl versions being pulled into the same
RSS (which is quite common for bigger components like qtbase).

If you really need to use openssl10 and have components which require
it, then you can temporary rename openssl10 recipe as openssl in our
layer to overlay 1.1 version from oe-core and use this openssl-1.0
everywhere (there aren't many packages which would be compatible with
openssl-1.1 and incompatible with openssl-1.0 - from the layers I have
included in my world build I know about these:

PNBLACKLIST[wvstreams] ?= "not compatible with openssl-1.0 since https://github.com/apenwarr/wvstreams/commit/5506a74e1b033776ad441b4554716cdcfa88fe03 which was backported to meta-oe and later reverted in upstream"
PNBLACKLIST[wvdial] ?= "depends on blacklisted wvstreams"
PNBLACKLIST[python3-m2crypto] ?= "not compatible with openssl-1.0"
PNBLACKLIST[python-m2crypto] ?= "not compatible with openssl-1.0"
PNBLACKLIST[rtmpdump] ?= "not compatible with openssl-1.0"
PNBLACKLIST[libtorrent] ?= "not compatible with openssl-1.0"
PNBLACKLIST[freeradius] ?= "not compatible with openssl-1.0"
PNBLACKLIST[rtorrent] ?= "depends on blacklisted libtorrent"
PNBLACKLIST[openlmi-tools] ?= "depends on blacklisted python-m2crypto"
PNBLACKLIST[python-pywbem] ?= "depends on blacklisted python-m2crypto"

and in all these cases it's simple to revert them to older from which
was compatible with openssl-1.0 before big bang.

But this work around should be only temporary and you should really try
to get rid of openssl10 soon.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  parent reply	other threads:[~2019-06-18 21:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 20:29 openssl10 in warrior Jonathan Richardson
2019-06-18 20:57 ` Alexander Kanavin
2019-06-18 21:29 ` Martin Jansa [this message]
2019-06-18 22:58   ` Jonathan Richardson

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=20190618212956.GD1501@jama \
    --to=martin.jansa@gmail.com \
    --cc=jonathan.richardson@broadcom.com \
    --cc=poky@yoctoproject.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.