From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a
Date: Thu, 17 Jan 2019 19:43:39 +0100 [thread overview]
Message-ID: <20190117194339.5cb2eb0f@gmx.net> (raw)
In-Reply-To: <20190116135821.pbjzcpixjbuacu3o@vkochan-ThinkPad-T470p>
Hello Vadim,
On Wed, 16 Jan 2019 15:58:21 +0200, Vadim Kochan <vadim4j@gmail.com> wrote:
[...]
> >
> > - Compile checked packages (depending explicit on libopenssl or host-libopenssl):
> > O.k:
> > - hostapd
> > - libpjsip
> > - mosquitto
> > - wpa_supplicant
> >
> > Failure:
> > - softether/host-softether
> >
> > - Compile checked packages (depending on openssl or host-openssl):
> > O.k.:
> > - alljoyn-base
> > - apr
> > - apr-util
> > - freeswitch
> > - openssh
> >
> > Failure:
> > - android-tools
> > - apache (CMake configure errro, unrelated?)
> >
> > [2] http://lists.busybox.net/pipermail/buildroot/2017-August/200859.html
> > [3] http://lists.busybox.net/pipermail/buildroot/2017-August/200898.html
> > ---
>
> Just some worries, I was trying to port openssl 1.1.x for one of the
> project and there were some issues with API compatibility for example
> for openssh (and mey be some other like curl, wget), it was an year ago
Openssh and wget are fixed (by update) already, did not yet test curl...but
I think the situation improves as some major linux distributions did already
the openssl update (or work on the update)...
> and may be mostly the packages switched to openssl 1.1.x API but
> it is not better to make openssl 1.1.x as one of the openssl provider
> to do not break other packages ?
Maybe the way to go in case to much packages will fail with openssl 1.1.x...
Identified ~200 buidlroot packages to (optional) depend on openssl...
Regards,
Peter
>
> Best regards,
> Vadim Kochan
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2019-01-17 18:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 22:42 [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a Peter Seiderer
2019-01-15 22:42 ` [Buildroot] [PATCH v4 2/2] freeswitch: bump to git master 8f10ae54a18a19fc6ed938e4f662bd218ba54b5e Peter Seiderer
2019-01-16 1:40 ` [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a Ryan Coe
2019-01-16 11:46 ` Arnout Vandecappelle
2019-01-16 14:27 ` Peter Seiderer
2019-01-16 5:52 ` Baruch Siach
2019-01-16 13:58 ` Vadim Kochan
2019-01-17 18:43 ` Peter Seiderer [this message]
2019-01-22 11:23 ` Arnout Vandecappelle
2019-01-22 21:08 ` Peter Korsgaard
2019-01-23 14:29 ` Arnout Vandecappelle
2019-01-23 16:15 ` Peter Korsgaard
2019-01-23 22:44 ` Arnout Vandecappelle
2019-01-23 23:03 ` Peter Korsgaard
2019-01-25 23:27 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2019-01-16 11:43 Patrick Havelange
2019-01-16 14:24 ` 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=20190117194339.5cb2eb0f@gmx.net \
--to=ps.report@gmx.net \
--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