I thought, the EMTHREAD issue is a known bug in the development master of zeormq. But Martin's comment makes me think this bug is only in the old sustrik/zeromq2 repo. What is the status of this bug?
Brian On Wed, Jul 7, 2010 at 9:24 PM, rad jan <[email protected]> wrote: > Hi, Brian, > I followed the instructions on this page > (http://www.zeromq.org/bindings:python). > Use the master of http://github.com/sustrik/zeromq2 > pyzmq would give such error while installing. > zmq/_zmq.c: In function ‘init_zmq’: > zmq/_zmq.c:10242: error: ‘EMTHREAD’ undeclared (first use in this function) > zmq/_zmq.c:10242: error: (Each undeclared identifier is reported only once > zmq/_zmq.c:10242: error: for each function it appear > But I think I might use the wrong git repo. > As a zeromq user, should I use the master > of http://github.com/zeromq/zeromq2? > I did a simple test, and pyzmq works fine with it. > Thanks > Rad > 2010/7/2 Brian Granger <[email protected]> >> >> HI, >> >> Thanks for the report. It looks like there are number of significant >> regressions in dev master right now. I am trying to track down some >> of them. Could you file an issue on github for this bug here: >> >> http://github.com/zeromq/zeromq2/issues >> >> Thanks, >> >> Brian >> >> On Thu, Jul 1, 2010 at 6:25 AM, rad jan <[email protected]> wrote: >> > Hi, Martin, >> > It appears that I cant install pyzmq base on the trunk version now. >> > So I just replaced tcp_connector.cpp of zmq 2.0.7 with the trunk >> > version. >> > And It works fine. >> > Thanks for your help. >> > >> > 2010/7/1 Martin Hurton <[email protected]> >> >> >> >> I think this is fixed on the master now? Can you checkout using GIT >> >> and test this version? >> >> >> >> - Martin >> >> >> >> On Thu, Jul 1, 2010 at 6:03 AM, rad jan <[email protected]> wrote: >> >> > Hi, folks, >> >> > Thanks for your great work! >> >> > We use zmq as the message system between modules on different >> >> > servers. >> >> > The servers are in an unreliable environment, e.g. I may connect to a >> >> > server >> >> > but its actual state is down or some server's network may fail for a >> >> > while. >> >> > There are two circumstances where I get assertion failed. >> >> > 1. When I tried to connect to a server that has not started yet. >> >> > (Does >> >> > not >> >> > happen all the time) >> >> > 2. When a connected server's network is failed. >> >> > I am using zmq2.0.7 with python binding. >> >> > Here is some sample code: >> >> >>>> import zmq >> >> >>>> c = zmq.Context() >> >> >>>> addrs = ['tcp://10.1.169.55:6666', 'tcp://10.1.169.57:6666', >> >> >>>> 'tcp://10.1.168.210:6666'] >> >> >>>> sockets = [] >> >> >>>> for addr in addrs: >> >> > ... s = c.socket(zmq.XREQ) >> >> > ... s.connect(addr) >> >> > ... sockets.append(s) >> >> >>>> Assertion failed: err == ECONNREFUSED || err == ETIMEDOUT >> >> >>>> (tcp_connecter.cpp:296) >> >> > Terminated (core dumped) >> >> > Is there any way to get rid of this error? >> >> > _______________________________________________ >> >> > zeromq-dev mailing list >> >> > [email protected] >> >> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> >> > >> >> > >> >> _______________________________________________ >> >> zeromq-dev mailing list >> >> [email protected] >> >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > >> > >> > _______________________________________________ >> > zeromq-dev mailing list >> > [email protected] >> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > >> > >> >> >> >> -- >> Brian E. Granger, Ph.D. >> Assistant Professor of Physics >> Cal Poly State University, San Luis Obispo >> [email protected] >> [email protected] >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > -- Brian E. Granger, Ph.D. Assistant Professor of Physics Cal Poly State University, San Luis Obispo [email protected] [email protected] _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
