From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] zeromq: bump to version 4.0.1
Date: Tue, 08 Apr 2014 07:38:45 -0300 [thread overview]
Message-ID: <5343D1B5.6090302@zacarias.com.ar> (raw)
In-Reply-To: <CAKAx1ciJq-EiGYcQEDHzVn5AfvaXE_dQ1ohYO_QLwi=ndEqL4g@mail.gmail.com>
On 04/08/2014 07:28 AM, Lionel Orry wrote:
>> Hi.
>> It breaks at least openvpn since the API isn't 100% compatible with the
>> 1.2.x series and openvpn doesn't handle 1.3.x yet.
>> Hiawatha has a new version which bundles/works with 1.3.x.
>> I haven't tried with libcurl but my gut tells me it should work since
>> they update often.
>> Dunno about rtmpdump.
>> It may be possible to make them live side-by-side by making a polarssl13
>> package, though it may need to reside in a non-default prefix.
>> Another possible solution is to fetch openvpn patches from git to make
>> it compatible, but last time i checked (several months ago) there were
>> none - that may have changed though.
>> I'll take a look and get back a bit later.
>
> Thanks a lot. In the meantime, I asked upstream for the possibility to
> build a proper release tarball including the polarssl source code, so
> that the version bump would not be necessary.
openvpn git mater is a no go, same with rtmpdump.
If they ship the tarball that'd be great, otherwise we can look into
packaging polarssl13.
Fortunately upstream still considers polarssl12 maintained and there are
security bumps if need be (not affected by the latest openssl/tls bug).
There's always the option of helping/patching the offending packages to
support it, but i'd rather not go there ;)
Or the last option of kicking the polarssl backend from them and just
keeping openssl/gnutls.
Regards.
next prev parent reply other threads:[~2014-04-08 10:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 16:31 [Buildroot] [PATCH 1/1] zeromq: bump to version 4.0.1 Jerzy Grzegorek
2014-03-01 22:25 ` Thomas Petazzoni
2014-03-03 6:51 ` Lionel Orry
2014-03-03 7:47 ` Thomas Petazzoni
2014-03-03 8:14 ` Lionel Orry
2014-03-03 10:11 ` Thomas Petazzoni
2014-04-07 14:32 ` Thomas De Schampheleire
2014-04-07 15:07 ` Lionel Orry
2014-04-08 7:32 ` Lionel Orry
2014-04-08 10:13 ` Gustavo Zacarias
2014-04-08 10:28 ` Lionel Orry
2014-04-08 10:38 ` Gustavo Zacarias [this message]
2014-04-08 18:43 ` Lionel Orry
2014-04-11 7:03 ` Lionel Orry
2014-04-11 7:35 ` Peter Korsgaard
2014-04-11 7:39 ` Peter Korsgaard
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=5343D1B5.6090302@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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