From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>, Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: openssl10 unusable for many components
Date: Mon, 21 Aug 2017 10:29:47 +0100 [thread overview]
Message-ID: <1503307787.32591.59.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQcQNkYbnSpVzA5xceo=CTpWDnKd8n3WaZM6zbUOe5m_XA@mail.gmail.com>
On Fri, 2017-08-18 at 19:29 +0200, Martin Jansa wrote:
> Even with that patch to rename openssl10 back to openssl we still
> need to solve the openssl-native which wasn't reverted back to 1.0.
>
> Upstream nodejs isn't going to be openssl-1.1 for a bit longer as
> explained:
> https://github.com/nodejs/node/pull/14761
> https://github.com/nodejs/node/pull/11828
> so it would make sense to revert native and nativesdk versions as
> well - if it isn't done in oe-core, I'll do it in our own layers to
> keep the builds going.
Hopefully we have a working 'revert' back to 1.0 in master now as there
was simply too much breakage for this release.
I would ask that people do try and figure out how to solve some of the
1.1 issues in the meantime, hopefully people can enable 1.1 with some
PREFERRED_VERSION tweaks.
Cheers,
Richard
next prev parent reply other threads:[~2017-08-21 9:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 10:31 openssl10 unusable for many components Martin Jansa
2017-08-17 11:23 ` Alexander Kanavin
2017-08-17 11:33 ` Richard Purdie
2017-08-17 11:46 ` Martin Jansa
2017-08-17 11:54 ` Alexander Kanavin
2017-08-18 5:56 ` Khem Raj
2017-08-18 10:53 ` Alexander Kanavin
2017-08-18 14:41 ` Khem Raj
2017-08-18 17:29 ` Martin Jansa
2017-08-18 17:56 ` Mark Hatle
2017-08-18 18:41 ` Alexander Kanavin
2017-08-18 18:55 ` Martin Jansa
2017-08-18 19:03 ` Mark Hatle
2017-08-18 18:19 ` Alexander Kanavin
2017-08-21 9:29 ` Richard Purdie [this message]
2017-08-21 9:59 ` Martin Jansa
2017-08-18 18:15 ` Alexander Kanavin
2017-08-18 17:41 ` Martin Jansa
2017-08-18 18:30 ` Alexander Kanavin
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=1503307787.32591.59.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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