I have run up a fresh Ubuntu 14.04.3 install didn't see any issues
(once I figured out what packages to install to get the tests all
running). Can you elaborate on the problem you are seeing?
Robbie
On 12 August 2015 at 22:41, Andrew Stitcher astitc...@redhat.com wrote:
I've tested proton-c on
[
https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-952.
Resolution: Fixed
Building Proton with python 2.6 and python 3.4 on Travis CI finds and
[
https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695979#comment-14695979
]
ASF subversion and git services commented on PROTON-952:
Commit
I've now figured out the issue (and it's an instructive problem):
PROTON-979: [1]
It seems that both OpenSSL and Cyrus SASL have interacting global
state. If SASL gets to initialise libcrypto first then when the SSL
code tries to do it it fails.
Just another emphasis that neither openssl nor
Great, well done figuring it out!
Care to vote yet? :)
Robbie
On 13 August 2015 at 21:16, Andrew Stitcher astitc...@redhat.com wrote:
I've now figured out the issue (and it's an instructive problem):
PROTON-979: [1]
It seems that both OpenSSL and Cyrus SASL have interacting global
state.
I vote +1:
I've tested proton-c python on:
Ubuntu 12.04 (amd64)
Ubuntu 14.04 (amd64/i686)
Raspberry Pi2 (Raspbian Jesse)
FreeBSD 10.1p17
Windows 8.1 with Visual Studio 12 (2013)
[Some of these test have had Java tox as well but it's been uneven)
And modulo some (severe) irritations (see the
