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:13:35 -0300 [thread overview]
Message-ID: <5343CBCF.8080103@zacarias.com.ar> (raw)
In-Reply-To: <CAKAx1ch=rxf=EfCfntHxqfsV4jQEU1asj9JTQ4odMhrD2xZJEA@mail.gmail.com>
On 04/08/2014 04:32 AM, Lionel Orry wrote:
> Quick news : mongrel v1.9.0 depends on polarssl now. But they decided
> to declare this dependency as a git submodule of their repo, and the
> release tarball being taken directly from github does not include the
> polarssl code. In short, they release tarball is unuseable. I'll talk
> about it upstream.
>
> To make it clean, I'll try to get rid of the git submodule dep and
> make attempts with the polarssl buildroot package.
>
> The bad (or not?) news is that mongrel2 depends on polarssl v1.3.0
> (v1.3.x if polarssl properly versions its library, I think it is the
> case) and we currently use polarssl v1.2.10, so a polarssl bump
> version is needed first.
>
> Does anyone know what implications could a polarssl minor version bump
> have ? I already saw some of the polarssl patches don't apply properly
> so they need to be revisited. Gustavo, I think you were in charge of
> the last polarssl bump, do you think you could help with this one, or
> say whether it is a very bad idea to bump the package version ?
>
> Thanks everyone,
> Lionel
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.
Regards.
next prev parent reply other threads:[~2014-04-08 10:13 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 [this message]
2014-04-08 10:28 ` Lionel Orry
2014-04-08 10:38 ` Gustavo Zacarias
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=5343CBCF.8080103@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