From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1 1/2] libopenssl: bump version to 1.1.0h
Date: Sun, 29 Apr 2018 15:00:45 +0200 [thread overview]
Message-ID: <t8sgrexjul.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20180417211921.18718-1-ps.report@gmx.net
Am Tue, 17 Apr 2018 23:19:20 +0200 schrieb Peter Seiderer:
> --- a/package/libopenssl/libopenssl.mk
> +++ b/package/libopenssl/libopenssl.mk
> @@ -4,7 +4,7 @@
> #
>
################################################################################
>
> -LIBOPENSSL_VERSION = 1.0.2o
> +LIBOPENSSL_VERSION = 1.1.0h
> LIBOPENSSL_SITE = http://www.openssl.org/source
> LIBOPENSSL_SOURCE = openssl-$(LIBOPENSSL_VERSION).tar.gz
> LIBOPENSSL_LICENSE = OpenSSL or SSLeay
Hi Peter,
freeswitch will need a bump to its master branch, the current release
version 1.6.20 is not compatible with openssl 1.1.x. I am using the
master branch for months now without problems.
To build ca-certificates the libopenssl package needs this upstream
patch: https://github.com/openssl/openssl/
commit/00701e5ea84861b74d9d624f21a6b3fcb12e8acd Otherwise you will run
into https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894282
Regards, Bernd
next prev parent reply other threads:[~2018-04-29 13:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 21:19 [Buildroot] [RFC v1 1/2] libopenssl: bump version to 1.1.0h Peter Seiderer
2018-04-17 21:19 ` [Buildroot] [RFC v1 2/2] openssh: add patch to fix openssl-1.1.0h compile Peter Seiderer
2018-04-20 15:29 ` [Buildroot] [RFC v1 1/2] libopenssl: bump version to 1.1.0h Ryan Coe
2018-04-29 8:17 ` Bernd Kuhls
2018-05-02 21:25 ` Peter Seiderer
2018-05-02 21:14 ` Peter Seiderer
2018-04-29 13:00 ` Bernd Kuhls [this message]
2018-05-03 21:05 ` Peter Seiderer
2018-05-01 7:46 ` Bernd Kuhls
2018-05-02 21:35 ` Peter Seiderer
2018-05-02 7:21 ` Thomas Petazzoni
2018-05-03 21:11 ` Peter Seiderer
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=t8sgrexjul.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--cc=buildroot@busybox.net \
/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