Yes, I am sad to say so.
The problem is that I never really contributed.
I did attempt once in the very beginning when I naively wrote a Windows
Office document detailing how to get and build the several ZeroMQ projects
in the Windows environment, but my PR was rejected because it contained a
That said, I'll have a look and see if I can add a +draft to the
version number of draft builds in OBS so that they work out as higher.
Given they are in a separate repo it's reasonable to assume they are
intended to have priority.
On Wed, 26 Sep 2018 at 22:06, Luca Boccassi wrote:
>
> The -X is
The -X is added because this is how versioning in distribution works:
https://www.debian.org/doc/debian-policy/ch-controlfields.html#version
The reason for a separate build for draft APIs is that they can change
at any moment without any warning in an incompatible way and break
existing
Ah thx, for that option. I was just wondering, why the hell ubuntu is
adding -1 to their version. Its probably the same version as your stable
versionin your repo, right?
The actual best solution in my opinion would be to have a
libzmq3draft-dev and libzmq5draft in ubuntu as well...
So I
Luca:
All your points are well-taken; there are plenty of times I wish we were less
strict, but in the long run it works for us — because it has to.
And you’re right that neither libsodium nor openpgm are part of core
RedHat/CentOS — both are supplied by EPEL. We make an exception for those
The dependencies are added on OBS only when missing in the base system.
As far as I'm aware RHEL was missing sodium, or at least it was the
last time I checked. If that's not the case then just report it and we
can remove the downstream build.
It's fine to have a corner case like yours, with
Right, I thought you were using the rolling one, my bad.
In that case you can add the following to /etc/apt/preferences.d/zmq
Package: *
Pin: origin download.opensuse.org
Pin-Priority: 1000
Priority of 1000 means that it will install packages from that origin
even if they are technically
Are we loosing you?
On Wed, Sep 26, 2018, 17:55 Osiris Pedroso wrote:
> ___
> zeromq-dev mailing list
> zeromq-dev@lists.zeromq.org
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
___
zeromq-dev
Well... thats not the case for "release-draft". There it is 4.2.5 and
ubuntu provides 4.2.5-1.
Doh!
On 26.09.2018 18:02, Luca Boccassi wrote:
The packages from OBS have a higher version so they already have
priority:
$ dpkg --compare-versions 4.2.5+git20180922 gt 4.2.5-1 && echo true ||
The packages from OBS have a higher version so they already have
priority:
$ dpkg --compare-versions 4.2.5+git20180922 gt 4.2.5-1 && echo true || echo
false
true
So either you haven't ran apt upgrade, or you have manually pinned it down,
check with:
apt-cache policy libzmq5
On Wed,
Hi Luca:
The problem, for me at least, is that some of the library versions required by
the packaged ZeroMQ are not native for the target OS.
For instance, the 4.2.5 distro for RH6 requires libsodium.so.18, while the
native version on RH6 is libsodium.so.4. A similar situation exists with
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
Update:
I investigated my .so files with "readelf -Ws" and "objdump -T" and both
say that there are no draft api symbols. Nevertheless, when I download
the deb package from zeromq's repo and investigate the libraries in
there with the same tools, it matches.
So regarding the dynamic
In case the base system is missing a dependency, everything that is
needed is shipped in the same repository where the library can be
found, and kept up to date.
Please do not recommend to avoid repositories - it's the preferred form
of distribution for Linux users.
On Wed, 2018-09-26 at 11:22
So I guess you could use the static lib, but that may not be ideal.
Personally I’ve had problems with the packaged builds — e.g., the RH builds
require specific versions of dependent libs that are not native to the OS. For
that reason, among others, I build libzmq from source. That’s not easy
And so does the shared library:
$ objdump -T libzmq.so.5.1.5 | grep msg_group
00075a60 gDF .text 0005 Basezmq_msg_group
Make sure you have actually installed it from that repository and not
from Ubuntu's.
On Wed, 2018-09-26 at 17:10 +0200, Stephan again wrote:
And the static library installed from this repository seems to have the
draft api included. Here is the test for that:
nm -gC /usr/lib/x86_64-linux-gnu/libzmq.a | grep zmq_msg_group
nm: src_libzmq_la-devpoll.o: no symbols
nm: src_libzmq_la-gssapi_mechanism_base.o: no symbols
nm:
I Installed it from:
http://download.opensuse.org/repositories/network:/messaging:/zeromq:/release-draft/xUbuntu_18.04/
Hoping that it was compiled accordingly...
This:
g++ Discovery.cpp /usr/lib/x86_64-linux-gnu/libzmq.a -lpthread
-DZMQ_BUILD_DRAFT_API=1 -DENABLE_DRAFTS=On -o test
makes
Jake is correct — the ENABLE_DRAFTS flag is used when *building* ZeromMQ, not
when linking against the library.
Where did your ZeroMQ come from? Did you build it from source, or take a
pre-packaged build? If the latter, it was likely built *without* draft
support, and you will need to
ZeroMQ itself needs to be compiled with ENABLE_DRAFTS in CMake. You've
added it to the compiler flags when building your own application. Did you
compile ZeroMQ yourself or are you using a distro-provided version?
For the static library, one way is to give the full path to the .a file
instead
Hi Bill,
adding -DENABLE_DRAFTS=On does not help:
g++ Discovery.cpp -lzmq -DZMQ_BUILD_DRAFT_API=1 -DENABLE_DRAFTS=On -o test
I also checked my installed libraries with "nm -gC zmq_msgs_group":
/usr/lib/x86_64-linux-gnu/libzmq.a -> match
/usr/lib/x86_64-linux-gnu/libzmq.so -> no match
Hi Stephan:
The RADIO/DISH sockets are considered DRAFT, which is probably why you’re
getting these errors.
There are a couple of possibilities:
- You may be linking against a version of libzmq that doesn’t include the draft
APIs. In order to build with draft support, the build needs to
Hi,
I asked this question/issue one and a half year ago
(https://lists.zeromq.org/mailman/private/zeromq-dev/2017-January/031309.html).
The difference is that I now would like to use zeromq (draft api)
version 4.2.5 under Ubuntu 18.04.
My minimal (not) working example can be found here:
Dear ZeroMQ community,
I am wondering if this behaviour is normal: zmq_send() is blocking on
ZMQ_STREAM when client has disconnected.
I have a simple server using a ZMQ_STREAM socket to serve plain TCP clients.
When a client disconnects, ZeroMQ effectively delivers a disconnection
indication
24 matches
Mail list logo
