-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please UPDATE gem to work with 0MQ 3.x.x ... current gem won't build w/ 3.0 #25
Comments
Second. Can't get the gem to build. Python is great. I have a reason to use ruby. zeromq 3.2 is stable and recommended for use with new projects, unless those projects are ruby? What's the deal? |
Can someone submit a pull request for 3.x support, please? Or coordinate with 0MQ leadership to take over as maintainer of this gem? I don't have any active projects using 0MQ at this time and have not been following the 3.x development, so I'm not even really sure what changed. |
Would also love to see this fixed. |
I pushed some changes to the "zeromq3" topic branch that make the build succeed with version 3.x of the zeromq library. Please test. |
Using the zeromq3 branch, the gem builds, but when I try to run the hwclient.rb I get "./hwclient.rb:17:in `send': Socket operation on non-socket (ZMQ::Error)" The changes I had to make to the hwclient.rb listing in the guide, to get this far, are;
|
@digitalronin did you found already a fix for this issue? |
I will put here the errors caused in "gem install zmq" in case someone want to work in a pull request. ERROR: Error installing zmq:
checking for zmq.h... yes make define ZMQ_EXPORT attribute ((visibility("default")))
rbzmq.c:1517:38: error: too few arguments to function call, expected 4, have 3 define ZMQ_EXPORT attribute ((visibility("default")))
rbzmq.c:1541:81: error: too few arguments to function call, expected 4, have 3 define ZMQ_EXPORT attribute ((visibility("default")))
rbzmq.c:1602:38: error: too few arguments to function call, expected 4, have 3 define ZMQ_EXPORT attribute ((visibility("default")))
rbzmq.c:1675:50: error: use of undeclared identifier 'ZMQ_HWM' define INT2NUM(v) INT2FIX((int)(v))
/Users/paulocheque/.rvm/rubies/ruby-1.9.3-p194/include/ruby-1.9.1/ruby/ruby.h:225:45: note: expanded from macro 'INT2FIX' define INT2NUM(v) INT2FIX((int)(v))
/Users/paulocheque/.rvm/rubies/ruby-1.9.3-p194/include/ruby-1.9.1/ruby/ruby.h:225:45: note: expanded from macro 'INT2FIX' define INT2NUM(v) INT2FIX((int)(v))
/Users/paulocheque/.rvm/rubies/ruby-1.9.3-p194/include/ruby-1.9.1/ruby/ruby.h:225:45: note: expanded from macro 'INT2FIX' define INT2NUM(v) INT2FIX((int)(v))
/Users/paulocheque/.rvm/rubies/ruby-1.9.3-p194/include/ruby-1.9.1/ruby/ruby.h:225:45: note: expanded from macro 'INT2FIX' |
I can build from the zeromq3 branch fine, but I'm getting the 'Socket operation on non-socket' error as well. Ruby 1.9.3, 0MQ 3.2.3. |
We really need this too, please consider fixing this! |
@MSch I'm currently running this gem with no problems, using the version included in the latest pull request I've made. It might work for you guys. |
I got a same exception on ruby1.9.3. #!/usr/bin/env ruby require 'rubygems' context = ZMQ::Context.new 1 socket = context.socket ZMQ::REQ puts 'starting connect a tcp zmq server' socket.connect('tcp://127.0.0.1:5555') socket.send 'hello' |
@xjmarui What exception did you see? Your code works fine for me. |
The 3.0 guide is brilliant and I find it humorous. However, if you have a link to the 2.1.x guide - I might get more use out of that.
Currently, this gem will only work with 2.1.x zeromq and won't build on my system with 3.2.x for love or money. ... A lot of "ZMQ_HWM, ZMQ_SWAP, .." undeclared errors.
2.1.x is nice, and it is all good fun until you actually try to follow along at home with the web example code ... Poller? What's that in 2.x.x? That, and the break of API should have got this gem updated some time ago, or at least gotten a zmq3 gem out in the wild by now. Just saying.
-or-
if there is some magic incantation I'm just unaware of ... let me know the secrets of the universe, my gem won't build.
Thanks, and great work on the 3.0 guide - excellent.
The text was updated successfully, but these errors were encountered: