From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/luvi: add patch to fix build issue with OpenSSL 1.1.1a
Date: Thu, 14 Feb 2019 09:43:06 +0100 [thread overview]
Message-ID: <20190214094306.0a28abb3@windsurf> (raw)
In-Reply-To: <20190213220812.29978-1-joerg.krause@embedded.rocks>
Hello,
On Wed, 13 Feb 2019 23:08:11 +0100
J?rg Krause <joerg.krause@embedded.rocks> wrote:
> Bump the bundled lua-openssl version to 0.7.4 for compatibility with
> OpenSSL 1.1.1a.
>
> Note, that luvi 2.7.6 is the latest version providing a release tarball.
>
> Runtime tested on Banana Pro, note that version string for lua-openssl
> does not match the tag name (0.7.4):
>
> ```
> luvi v2.7.6
> zlib: 1.2.11
> libuv: 1.25.0
> ssl: OpenSSL 1.1.1a 20 Nov 2018, lua-openssl 0.7.3
> ```
>
> Fixes:
> http://autobuild.buildroot.net/results/e87994a3dc987f5aa101a5e721ac927e21453373
> http://autobuild.buildroot.net/results/ea725ad90cfcd3c5e242268a593dcabd7297fe70
> http://autobuild.buildroot.net/results/f2fb9eea0044e4a5f674742d29ea95af49cf5a45
> http://autobuild.buildroot.net/results/de4daa1b930f907f06640dc98a708016217ddea5
> .. and many more.
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
This is really a huge patch.
Why is luvi using a bundled lua-openssl version instead of some
external lua-openssl package ?
I see that the change has been applied upstream
(https://github.com/luvit/luvi/commit/0d5959a33cde81ed49314bd6c56f6906a83d2fa1),
which is good.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-14 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 22:08 [Buildroot] [PATCH] package/luvi: add patch to fix build issue with OpenSSL 1.1.1a Jörg Krause
2019-02-14 8:43 ` Thomas Petazzoni [this message]
2019-02-14 9:20 ` Jörg Krause
2019-02-19 20:46 ` Jörg Krause
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=20190214094306.0a28abb3@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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