> I have identified three issues regarding native build of zeromq-2.0.7 under 
> QNX6.4.1:
> 
> 1) I had to remove "crtbegin.o, -lc, -lcS, ..." stuff from the created libtool
>  file
> (this seems the same issue as reported on zmq mailing list about mixed g++/QCC
>  linkage)

Seems not to be necessary if you compile with qcc/QCC

> 2) -lcrypto link flag has to be added to perf/Makefile and devices/*/Makefile

OK

> 3) poll() seems not to work. addind "#define ZMQ_FORCE_SELECT 1" to plattform.
> hpp,
> as suggested on the zmq mailing list does not help for me

It works for me ... this macro must be defined before the first compilation.

I could send you a complete Archive of a working version 2.0.7 .... send a mail to

armin at steinhoff dot de

--Armin

Just to make it clear ... these porting steps are OK with the previuos release of ZMQ.
The compilation of the module ctx.cpp of the version 2.0.7 terminates with a cryptic error ... it's a new module and 
must still be ported.

--Armin


> Piotr Trojanek wrote:
> > Yes,
> >
> > there is interest in ZMQ for QNX in my robotics team. I have seen your posts
>  on the zeromq-dev mailing list...
> >
> > At the moment I am trying to make a pkgsrc build of ZMQ, but there are some 
> minor linking issues...
> >
> > Best regards,
> >   
> Here are my porting steps:
> 
> - configure command for C bindings:  "CC=qcc CXX=QCC configure --with-c --with
> -perf"
>  
> - add to platform.hpp:
> 
> #define rpl_malloc malloc
> #define ZMQ_FORCE_SELECT 1 // polling doesn't work
> 
> - modify the LIBS specification of the Makefile located in perf to 
>    "LIBS = -lcpp -lcxa -lssl -lsocket"
> 
> if you link the latency apps with qcc 
> 
> --Armin
> 
> 
>